Linked API

ignore_invitation

Ignores an incoming connection, company-follow, or newsletter-subscription invitation (st.ignoreInvitation action). Set invitationType and provide only its matching URL. If this workflow is still running, do not retry this tool; retrying can queue duplicate ignore 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": "ignore_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 ignore.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 29, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations only say readOnlyHint=false and openWorldHint=true; the description goes far beyond by disclosing that the call is queued into a cloud-browser workflow, returns immediately with a pending/running status object, and can take minutes. It defines pendingReason semantics ('queued' vs 'outsideWorkingHours'), explains the outside-working-hours case returns immediately instead of polling, and names get_workflow_result with workflowId/operationName as the retrieval path.

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

Conciseness4/5

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

Front-loaded with what the tool does and how to call it, then the async lifecycle, then the pendingReason branches — a sensible information hierarchy. The no-retry warning is stated twice (paragraph one and paragraph two), which is the only genuinely removable repetition.

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 fire-and-forget workflow tool with no output schema, the description covers everything needed: the immediate return shape, how to poll via get_workflow_result, the polling termination condition, and how to report a parked workflow to the user. No material gap remains for correct invocation and follow-up handling.

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 the schema already documents all four fields and the enum. The description still adds a cross-field rule the schema cannot express: provide only the URL matching the chosen invitationType, which resolves the conditional-required ambiguity between personUrl, companyUrl, and newsletterUrl.

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 (ignore) plus the resource and enumerates all three invitation kinds handled (connection, company-follow, newsletter-subscription), plus the underlying action name. An agent can immediately separate this from accept_invitation and withdraw_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 supply only its matching URL — and explicit retry exclusions ('do not retry this tool' while a workflow is running). It never explicitly names accept_invitation as the counterpart for the opposite decision, so routing logic is inferred rather than stated.

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.