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 scheduled action is awaiting the execution horizon

scheduler_status: "awaiting_horizon" means the action is safely persisted but is still more than seven days away. SalesTouch registers its exact execution event automatically when it enters the supported horizon.

pending_retry means event registration will be retried by the hourly recovery process. Check status with queue details for the current effective time and any reconnect error.

If execution returns linkedin_reconnect_required, the stored LinkedIn session needs human intervention. Credential-based accounts normally reconnect automatically; legacy cookie sessions cannot.

A scrape result is too large

Scrape tools persist people or company items and return a limited preview. Use scrape_result_page with the returned result_id and cursor. Use the signed CSV or JSONL export for the full dataset; do not paste an entire export into the agent context.

By default, scrape_linkedin_post_comments extracts authors of root comments only. Set include_replies: true when authors of replies are also required; every reply thread needs additional LinkedIn requests and can make extraction substantially slower. Large comment scrapes automatically pause after a bounded number of source requests so the MCP call can finish within its transport window. source_stats.partial_reason is provider_request_budget when this safety boundary is reached or provider_interruption when LinkedIn interrupts a later request. In both cases, confirmed progress is preserved: when source_paging.exhausted is false, call the tool again with source_paging.arguments. Its opaque source_cursor resumes LinkedIn pagination in the same reply mode instead of starting over. The call can therefore return fewer profiles than limit. scrape_result_page only pages through profiles already stored by one extraction call.

A Sales Navigator filter is ambiguous

Call linkedin_sales_navigator_search_parameters with the reported parameter type and query. Select the intended candidate id, then retry the structured search with { "id": "..." }. Parameter ids depend on the connected Sales Navigator account, so do not invent or reuse an unverified id.

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.