> ## Documentation Index
> Fetch the complete documentation index at: https://docs.firsttouch.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> For API operations, fetch https://gateway.firsttouch.ai/api/public/openapi.json for the complete input/output schemas, internal references, and x-mcp-annotations. Endpoint Markdown intentionally omits generated schema fragments. Select /api/public/tools/<tool_name> using the exact underscore-separated name. Send requests to https://gateway.firsttouch.ai; the canonical document currently omits servers. Start at https://docs.firsttouch.com/api-reference/agent-start.md.

# List Team Members

> Call get_guide with topic=senders_and_capabilities before selecting flow candidates or Dynamic Action assignees.

<details>
<summary><strong>Detailed usage guidance</strong></summary>
<ul>
<li>Lists active members of the current team with their FirstTouch user id, email, role, ownership, user-facing access level (Paid sender or View-only), connected email accounts, LinkedIn account state, and flow-assignment permissions.</li>
<li>Paid sender seats allow account connections and sender actions.</li>
<li>Viewers can access the product, but cannot connect accounts, act as senders, or be assigned flow work.</li>
<li>For reusable flow plans, call this before choosing candidates: email requires isEmailConnected and isEmailSendingEnabled;<br />LinkedIn requires isLinkedinReady and isLinkedinActionsEnabled;<br />calls and manual tasks require their matching assignment permission;<br />every flow needs at least one selected candidate with isApprovalEnabled.</li>
<li>Use exact returned userIds in flow.candidates.</li>
<li>For dynamic actions, resolve every sender before calling add_dynamic_action: when no sender was requested, find the current user and select that member;<br />when named, compare the supplied identity with returned names, emails, and user ids;<br />when any capable sender is requested, select one eligible returned member and report who was chosen.</li>
<li>Pass that userId as action.assignedUserId.</li>
<li>Email requires isEmailConnected and Email actions permission.</li>
<li>LinkedIn connect/message/profile requires isLinkedinReady and Social actions permission; InMail also requires an eligible linkedinAccount.plan_type (Premium or Sales Navigator, subject to the team&#39;s Premium setting).</li>
<li>Calls and manual tasks require their matching permissions.</li>
<li>Do not use LinkedIn Unibox tools to choose a flow or dynamic-action sender.</li>
<li>isEmailConnected, isLinkedinConnected, and isLinkedinReady filters use AND semantics when combined.</li>
<li>LinkedIn ready means the account is alive and its relations sync has completed; dynamic actions validate the remaining capability requirements before creation.</li>
</ul>
</details>



## API Specification

The full API specification for this endpoint is available in the [documentation index](https://docs.firsttouch.com/llms.txt).