Skip to main content
Glama
Sign In

Linked API

by io.github.Linked-API
OverviewDiscussionsAdmin

retrieve_invitations

Read-only

Retrieves incoming connection, company-follow, and newsletter-subscription invitations received by your account (st.retrieveInvitations action). Every invitation carries urn — the permanent LinkedIn member URN (urn:li:member:) of the person who sent it, or null when LinkedIn does not expose it.

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

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "retrieve_invitations"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint; the description supplies the critical behavioral context those annotations cannot convey — that the call is queued into a cloud-browser workflow, returns immediately with a pending/running snapshot, and may take minutes. It also explains pendingReason values ('queued' vs 'outsideWorkingHours') and tells the agent to report a closed working-hours window to the user rather than loop.

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?

Three paragraphs, front-loaded with what is retrieved, then the async contract, then the pendingReason taxonomy — a logical progression with no filler. It is longer than typical, but nearly every sentence carries operational information the agent needs to avoid duplicate work or futile polling.

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?

With no output schema, no parameters, and annotations that say nothing about async execution, the description carries the full burden and meets it: it defines the immediate return shape, the follow-up tool, the timing semantics, and the failure/edge case of an out-of-hours parked workflow. Nothing needed to invoke or follow up correctly is missing.

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?

The tool takes zero parameters, so the baseline is 4 and there is no schema meaning to add. The description usefully notes that results carry a urn field (or null when LinkedIn does not expose it), which is return-value context rather than parameter semantics.

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

Purpose4/5

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

The description uses a specific verb (retrieves) and enumerates the exact resource set: incoming connection, company-follow, and newsletter-subscription invitations, plus the underlying st.retrieveInvitations action. The scope is unambiguous, though it does not explicitly contrast itself with the nearby sibling retrieve_pending_requests, which an agent could plausibly confuse it with.

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?

It gives concrete operational guidance: call get_workflow_result with the returned workflowId/operationName, and do not re-invoke the original tool while a workflow is running because that duplicates queued work. This is strong when-to-use/when-not-to guidance for the async flow, but it offers no guidance on choosing this tool over sibling retrieval tools.

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

All Linked API toolsInspect
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.

Resources