Linked API

accept_invitation

Accepts an incoming connection, company-follow, or newsletter-subscription invitation (st.acceptInvitation action). Set invitationType and provide only its matching URL. If this workflow is still running, do not retry this tool; retrying can queue duplicate accept attempts.

Linked API actions are queued into a cloud-browser workflow and may take several minutes. The server returns immediately after starting the workflow with {status: 'pending'|'running', pendingReason, workflowId, operationName, message}. To retrieve the final result, call get_workflow_result with the returned workflowId and operationName — it will long-poll until completion or the request budget elapses, then return either the final result or another in-progress snapshot. Do not retry the original tool while a workflow is still running; that creates duplicate queued work.

A pending workflow carries pendingReason: 'queued' means it is waiting its turn behind other work on the same account and will start within minutes. 'outsideWorkingHours' means the account has configured working hours and the workflow is parked until they reopen — possibly the next working day. In that case get_workflow_result returns immediately instead of polling, message states when the window opens, and you should report that to the user rather than looping.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "invitationType": "<invitationType>"
    },
    "name": "accept_invitation"
  }
}

Input Schema

Name	Required	Description
`personUrl`	No	Required only for invitationType 'connect'. Public or hashed LinkedIn URL of the person.
`companyUrl`	No	Required only for invitationType 'companyFollow'. LinkedIn company page URL.
`newsletterUrl`	No	Required only for invitationType 'newsletterSubscribe'. LinkedIn newsletter URL.
`invitationType`	Yes	Invitation type to accept.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 29, 2026

TDQS

A4.5/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Goes well beyond the annotations (readOnlyHint=false, openWorldHint=true) by disclosing that the action is queued into a cloud-browser workflow, may take minutes, and returns immediately with a status snapshot rather than a result. It also decodes pendingReason values ('queued' vs 'outsideWorkingHours'), explains that the latter may park until the next working day and returns immediately, and warns that retries queue duplicate accept attempts — exactly the behavioral context an agent needs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose and the type/URL pairing are front-loaded, which is good, but the do-not-retry warning is stated twice (paragraph one and paragraph three) and the pendingReason explanation is verbose. The length is defensible for an async workflow tool, yet a third of the text is repetition rather than new information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with no output schema, the description supplies the missing return contract (status, pendingReason, workflowId, operationName), the async retrieval path, and the retry hazard. Nothing an agent needs in order to call this correctly and follow up is absent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so per-parameter descriptions already exist, but the description adds a real constraint beyond the schema: provide only the URL matching the chosen invitationType, which clarifies the conditional-required semantics. It doesn't add format or validation detail for the URLs beyond what the schema states.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource set ('Accepts an incoming connection, company-follow, or newsletter-subscription invitation') and cites the underlying action (st.acceptInvitation). This clearly separates it from siblings such as ignore_invitation, retrieve_invitations, and send_connection_request without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete invocation guidance ('Set invitationType and provide only its matching URL') and explicitly routes follow-up work to get_workflow_result with the returned workflowId and operationName, plus a clear do-not-retry rule. It stops short of naming when an agent should prefer ignore_invitation or retrieve_invitations first, so the accept-vs-ignore decision is left implicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Linked API tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.