Linked API

fetch_company

Read-only

Allows you to open a company page to retrieve its basic information (st.openCompanyPage action). Can optionally retrieve employees, posts and decision makers. The basic information carries urn — the permanent LinkedIn organization URN of the company (urn:li:organization:); retrieved employees and decision makers carry their own member urn (urn:li:member:), and retrieved posts carry urn on their author and reposter. Each of them is null when LinkedIn does not expose the identifier.

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": {
      "companyUrl": "<companyUrl>"
    },
    "name": "fetch_company"
  }
}

Input Schema

Name	Required	Description
`companyUrl`	Yes	Public or hashed LinkedIn URL of the company. (e.g., 'https://www.linkedin.com/company/microsoft')
`retrieveDMs`	No	Optional. Whether to retrieve the company's decision makers information. Default is false.
`retrievePosts`	No	Optional. Whether to retrieve the company's posts information. Default is false.
`retrieveEmployees`	No	Optional. Whether to retrieve the company's employees information. Default is false.
`dmsRetrievalConfig`	No	Optional. Configuration for retrieving decision makers. Available only if retrieveDMs is true.
`postsRetrievalConfig`	No	Optional. Configuration for retrieving posts. Available only if retrievePosts is true.
`employeesRetrievalConfig`	No	Optional. Configuration for retrieving employees. Available only if retrieveEmployees is true.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 29, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Annotations only declare readOnly and openWorld; the description adds the queued cloud-browser execution model, the pending status envelope, the meaning of pendingReason 'queued' vs 'outsideWorkingHours', and the duplicate-work hazard of retrying. That is exactly the context annotations cannot convey.

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 purpose then the async contract then pending-state semantics. The urn paragraph is dense and slightly tangential to invocation, but it earns its place given there is no output schema.

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?

For a nested 7-parameter async tool with no output schema, the description explains the response envelope, how to retrieve results, and which identifiers appear in the payload. It stops short of describing the basic company fields themselves beyond urn, but overall an agent has enough to call 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% with descriptive text on every parameter and nested config, so the schema already carries parameter meaning. The description only restates the optional employee/post/decision-maker bundles rather than explaining limits or filter interaction beyond the schema.

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 states a concrete verb and resource ('open a company page to retrieve its basic information') and names the optional expansions (employees, posts, decision makers). It does not explicitly distinguish itself from siblings like search_companies or nv_fetch_company, so the agent must infer that this is the URL-addressed single-company fetch.

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 explicit operational guidance: results come back asynchronously, call get_workflow_result with workflowId and operationName, and do not retry the original tool while a workflow runs. What's missing is when to choose this over search_companies for finding a company in the first place.

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.