Linked API

fetch_post

Read-only

Open a LinkedIn post and retrieve its data, with optional comments and reactions. (st.openPost action). The 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 — and each retrieved reaction carries an actor object (type, name, urn, profileUrl or companyUrl, headline, and viewerState.connectionDegree for a person) with the same urn identity; each urn is null when LinkedIn does not expose the identifier. This action reads identifiers from the post page itself, so it resolves actor URNs that post listings such as retrieve_feed cannot. Comment authors carry no URN.

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": "fetch_post"
  }
}

Input Schema

Name	Required	Description
`postUrl`	No	LinkedIn URL of the post. (e.g., 'https://www.linkedin.com/posts/username_activity-id') Provide this or postUrn.
`postUrn`	No	URN of the post to fetch, as an alternative to postUrl. (e.g., 'urn:li:activity:1234567890123456789')
`retrieveComments`	No	Optional. When true, also retrieve comments for the post. Configure via commentsRetrievalConfig.
`retrieveReactions`	No	Optional. When true, also retrieve reactions for the post. Configure via reactionsRetrievalConfig.
`commentsRetrievalConfig`	No	Optional. Applies only when retrieveComments is true. Controls comments retrieval (limit, replies, sort).
`reactionsRetrievalConfig`	No	Optional. Applies only when retrieveReactions is true. Controls reactions retrieval (limit).

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?

Far beyond the annotations, it discloses that the call is queued into a cloud-browser workflow that may take minutes, the exact pending response shape, and the meaning of each `pendingReason` including `outsideWorkingHours` parking until the next working day. It also warns that retrying creates duplicate queued work, which is the key destructive-adjacent risk even for a read-only action.

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?

It is front-loaded with purpose and then the operational contract, with no filler sentences. The dense middle paragraph on URN identity is useful given there is no output schema, but it sits between the purpose and the async polling instructions, pushing the most operationally critical paragraph to second position.

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 compensates by describing what the returned author, reposter, and reaction actor objects contain and when their URNs are null. Combined with the async workflow contract and full schema coverage of the six parameters, an agent has what it needs to call this correctly.

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 coverage is 100%, so the schema already documents postUrl/postUrn, the retrieve flags, and the nested config limits and sort enum; the description adds no syntax or constraint detail beyond that. Notably, it never states the one-of requirement that either postUrl or postUrn must be supplied even though no parameter is marked required.

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?

The first sentence states a concrete verb and resource ("Open a LinkedIn post and retrieve its data") plus the optional expansions (comments, reactions). A later sentence explicitly positions it against the sibling `retrieve_feed`, explaining that this action resolves actor URNs from the post page that listing tools cannot.

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 clear post-invocation routing: call `get_workflow_result` with the returned workflowId and operationName, and explicitly warns not to retry the original tool while a workflow is running. It also distinguishes itself from `retrieve_feed` by capability. What it lacks is an explicit statement of when to prefer `search_posts` or the feed tools instead of opening a single post.

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.