Linked API

create_post

Creates a new LinkedIn post with optional mentions and media attachments (st.createPost action). Returns the URL and URN of the new post. If this workflow is still running, do not retry this tool; retrying can create duplicate posts.

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": {
      "text": "<text>"
    },
    "name": "create_post"
  }
}

Input Schema

Name	Required	Description
`text`	Yes	Post content, must be up to 3000 characters. Write "@[key]" where a mention should appear and describe that key in mentions.
`mentions`	No	People and companies to mention in the text. Each item binds a "@[key]" placeholder to one entity.
`companyUrl`	No	LinkedIn company page URL. If specified, the post will be created on the company page (requires admin access).
`attachments`	No	Media attachments for the post. You can add up to 9 images, or 1 video, or 1 document. Cannot mix different attachment types.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 29, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Substantially exceeds what readOnlyHint=false and openWorldHint=true convey: it discloses the queued cloud-browser workflow model, immediate pending response shape, multi-minute latency, duplicate-post risk on retry, and the working-hours parking case. The one notable omission is permission requirements for companyUrl posting, which is only covered inside the schema text.

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

Conciseness3/5

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

The critical no-retry warning is front-loaded, which is good, but it is then repeated almost verbatim in the next paragraph ('Do not retry the original tool while a workflow is still running; that creates duplicate queued work'). The multi-paragraph async-workflow boilerplate also crowds out tool-specific content like creating posts on company pages.

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 does the work of explaining the return shape ({status, pendingReason, workflowId, operationName, message}) as well as the final URL and URN. It is close to complete for a mutation tool, though it never states what a failure outcome looks like beyond pending states.

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% and the nested parameter descriptions are thorough (mention key binding, attachment mixing limits, company admin requirement). The description itself adds only a generic restatement ('optional mentions and media attachments'), so 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?

Opens with a specific verb and resource ('Creates a new LinkedIn post') plus the supported optional features (mentions, media attachments) and the underlying action name. It distinguishes the tool from read siblings but never contrasts it with the closely related create_repost sibling, which is the one realistic source of confusion.

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 an explicit when-not rule ('do not retry while the workflow is running') and names the successor tool to call with the returned workflowId and operationName. It also explains how to interpret pendingReason values, but offers no guidance on choosing create_post over create_repost.

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.