Linked API

retrieve_connections

Read-only

allows you to retrieve your connections and perform additional person-related actions if needed (st.retrieveConnections action). Every person in the result carries urn — their permanent LinkedIn member URN (urn:li:member:), 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_connections"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Optional. Number of connections to return. Defaults to 10, with a maximum value of 1000.
`since`	No	Optional. ISO date string that filters connections to only include those made on or after the specified date. Only works when filter is not provided.
`filter`	No	Optional. Object that specifies filtering criteria for people. When multiple filter fields are specified, they are combined using AND logic.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 29, 2026

TDQS

A3.9/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 goes well beyond that by disclosing the queued cloud-browser execution model, the immediate pending/running snapshot shape, the duplicate-work hazard, and what 'queued' vs 'outsideWorkingHours' pending reasons mean. The note that urn may be null is a useful data-quality caveat. No contradiction with the read-only annotation, since retrieving data may legitimately enqueue background work.

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?

Purpose is front-loaded, and the workflow lifecycle is broken into short, scannable paragraphs with the actionable rule (don't retry, poll with get_workflow_result) clearly stated. Minor waste in the vague "perform additional person-related actions if needed" clause, but almost everything else earns its place.

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

Completeness4/5

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

With no output schema, the description usefully sketches both the immediate return ({status, pendingReason, workflowId, operationName, message}) and a key result field (urn). It does not describe the shape of the remaining connection/person fields returned by get_workflow_result, so an agent must infer the final payload, but nothing needed to invoke the tool correctly is missing.

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

Parameters3/5

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

Schema description coverage is 100%, so the limit/since/filter semantics (including the AND combination of filter fields) are already fully documented in the schema. The description adds only the urn field note, which is a result-field detail rather than parameter meaning; baseline 3 applies.

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?

States a specific verb and resource ("retrieve your connections") and names the underlying action (st.retrieveConnections). The trailing clause about "additional person-related actions" is vague and blurs the purpose, and it never distinguishes itself from near-neighbours like get_network or sync_network, but the core operation is unambiguous.

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

Usage Guidelines3/5

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

Strong operational guidance for the async lifecycle: call get_workflow_result with workflowId/operationName, and do not retry the original tool while a workflow runs. However, there is no guidance on when to choose this over sibling tools such as sync_network, get_network, or search_people, so tool selection remains implied.

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.