Linked API

retrieve_feed

Read-only

Retrieves posts from the current account's personalized LinkedIn home feed (st.retrieveFeed action). Each post's author and reposter carry urn — a member URN (urn:li:member:) for a person actor and an organization URN (urn:li:organization:) for a company actor, or null when LinkedIn does not expose it in the feed; fetch_post resolves actor URNs this listing cannot.

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_feed"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Maximum number of posts to retrieve (default 20).

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 29, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Goes far beyond readOnlyHint/openWorldHint by disclosing that the action is queued into a cloud-browser workflow that may take minutes, the exact snapshot shape returned ({status, pendingReason, workflowId, operationName, message}), and the duplicate-work hazard of retrying. It also decodes both pendingReason values, including that 'outsideWorkingHours' means reporting the window to the user rather than looping.

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-loads the purpose, then splits async mechanics and pendingReason handling into separate paragraphs, which is the right structure for a multi-state workflow tool. It is on the long side and the URN paragraph could be tightened, but no sentence is truly filler.

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, the description still tells the agent what the immediate return looks like, how to obtain the final result, and how to interpret both pending states — everything needed to call it correctly and handle the response. The only minor omission is guidance on choosing it over search_posts.

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?

Only one parameter (limit, default 20, max 100) and the schema already documents it at 100% coverage, so the baseline is 3. The description adds no meaning about limit behavior — e.g., whether the cap interacts with feed pagination or whether larger limits increase workflow latency.

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 plus the scope constraint that matters most: 'posts from the current account's personalized LinkedIn home feed (st.retrieveFeed action)'. It also positions fetch_post as the tool for resolving actor URNs this listing cannot, so an agent can separate this from a generic post search.

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 explicit operational routing: after invoking, call get_workflow_result with the returned workflowId and operationName, and do not retry the original tool while a workflow is running. What it lacks is feed-vs-search guidance (e.g., when to prefer search_posts or retrieve_performance instead), so the when-not is only partially covered.

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.