> ## 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.

# Check your setup before LinkedIn outreach

> Verify your caller, team, sender, and workflow guidance with read-only FirstTouch MCP calls.

Before preparing outreach, check which FirstTouch team and sender your agent will use. This walkthrough covers the read-only setup checks after [connecting FirstTouch MCP](/WebApp/Mcp/connect).

The six requests below were executed through authenticated MCP on September 15, 2026, using a team-owner account with a connected sender. They verify the setup information returned by MCP. This walkthrough stops before creating or approving outreach and does not establish that a message will be delivered.

## 1. Check the caller and team

Call `get_current_user` with:

```json theme={null}
{}
```

Inspect `isAuthenticated`, `userId`, `teamId`, `permissions`, and `warnings`. Confirm that the returned user and team are the ones you intend to use. Keep the returned `userId` for the sender check below.

If the call fails or the identity is wrong, resolve the connection or account selection before continuing. Do not assume the current user is the intended sender.

## 2. Inspect the reported scopes

Call `get_auth_scopes` with:

```json theme={null}
{}
```

Read `caller`, `scopes`, and `warnings`. Each returned scope includes its name, a `granted` value, and a description. The response describes scopes inferred from the current request context. Treat it as setup information; verify the result of any later action separately.

## 3. Load the sender guidance

Call `get_guide` with:

```json theme={null}
{
  "topic": "senders_and_capabilities"
}
```

Read the returned **Senders and capabilities** guide before selecting a sender. It includes a table of the capability fields to inspect for the work you are planning.

## 4. Identify the intended team member

Call `list_team_members` with:

```json theme={null}
{}
```

Find the intended sender in `items`. Match their returned `userId` or email; a display name alone may be ambiguous. If the caller will be the sender, match the `userId` from step 1.

Inspect that member's `access`, `capabilities`, and returned connected-account details. For LinkedIn, locate `capabilities.isLinkedinReady` and `capabilities.isLinkedinActionsEnabled`. Record the actual values instead of inferring readiness from an account name.

If the member is missing, the identity is ambiguous, or the returned fields do not satisfy the guide's requirements, resolve that issue before preparing an action. Do not silently choose a different sender. The response also includes `uiLinks` for account connection and team management.

## 5. Load the workflow and review guidance

For the one-contact workflow, call `get_guide` with:

```json theme={null}
{
  "topic": "dynamic_actions"
}
```

Then load the task and review guidance:

```json theme={null}
{
  "topic": "tasks_and_approvals"
}
```

Both calls return Markdown guidance. Read the contact checks, action requirements, and review instructions before designing your next step. Retrieving those guides is a read check; it does not execute or test their outreach instructions.

## Review the result

You should now have:

* The intended caller and team, with any returned warnings reviewed.
* The intended sender's exact user ID and reported account capabilities.
* The current sender, one-contact workflow, and task guides.

Keep these findings separate from a send approval. Before testing outreach, agree on an internal recipient, exact message, sender, and whether the work should wait for review. Verify that complete workflow and its actual outcome before expanding it.

For operation-specific inputs, use the [operation catalog](/api-reference/operation-catalog). For handling action results, see [Execution and Recovery](/api-reference/execution-and-recovery).