Troubleshooting

The MCP is installed but no tools appear

Start a fresh task or conversation after connecting the server. MCP clients usually load tool definitions when a session begins, not continuously in an existing session.

Confirm that the configured endpoint is exactly:

https://www.salestouch.io/api/mcp

The client asks you to authenticate again

The access token is absent, expired, or lacks the required scope. Run the MCP login flow again, complete the browser consent, then create a fresh client session.

paid_plan_required

The user is authenticated, but the SalesTouch workspace does not have LinkedIn MCP access. This is an entitlement problem, not an OAuth transport problem.

No connected LinkedIn account

Connect LinkedIn in SalesTouch and verify with linkedin_accounts. Do not pass a guessed account_id.

A target cannot be resolved

Use the narrow lookup tool first:

• linkedin_lookup_profile for a member.
• linkedin_lookup_company for a company or school.
• linkedin_lookup_post for a post.

Prefer a full LinkedIn URL when a handle or provider identifier is ambiguous.

message_requires_connection

Direct messages normally require an existing LinkedIn relationship or known conversation. Use linkedin_invite or linkedin_invite_then_message instead.

action_limit_queue_required

SalesTouch protected the account from an immediate action. Repeat the same tool call with:

{
  "queue": true
}

Preserve the original target and content when retrying.

A scrape result is too large

Scrape tools persist their output and return a limited preview. Use scrape_result_page with the returned result_id and cursor. Do not paste an entire export into the agent context.

Tool results look like text instead of JSON

This is expected. SalesTouch returns MCP text content containing formatted JSON. The assistant should parse the text and present the useful result in its normal response.

Still blocked

Collect the tool name, sanitized input, error code, and approximate time from the SalesTouch activity log. Never include OAuth tokens, LinkedIn cookies, or private credentials in a support report.