Linked API

nv_fetch_company

Read-only

Allows you to open a company page in Sales Navigator to retrieve its basic information (nv.openCompanyPage action). Can optionally retrieve employees and decision makers. The basic information carries urn — the permanent LinkedIn organization URN of the company (urn:li:organization:) — and retrieved employees and decision makers carry their own member urn (urn:li:member:); each 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": {
      "companyHashedUrl": "<companyHashedUrl>"
    },
    "name": "nv_fetch_company"
  }
}

Input Schema

Name	Required	Description
`retrieveDMs`	No	Optional. Whether to retrieve the company's decision makers information. Default is false.
`companyHashedUrl`	Yes	Public or hashed LinkedIn company URL (/company/... or /sales/company/...).
`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.
`employeesRetrievalConfig`	No	Optional. Configuration for retrieving employees. Available only if retrieveEmployees is true.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 6, 2026

changedInput schema / properties / companyHashedUrl / description

Previous value: -"Hashed LinkedIn URL of the company."New value: +"Public or hashed LinkedIn company URL (/company/... or /sales/company/...)."

First observedOct 29, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Goes well beyond the readOnlyHint/openWorldHint annotations by disclosing that the action is queued into a cloud-browser workflow, may take several minutes, returns an immediate {status, pendingReason, workflowId, operationName, message} snapshot, and distinguishes 'queued' from 'outsideWorkingHours' parking behavior. It also warns that retrying creates duplicate queued work — exactly the kind of behavioral 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?

Purpose is front-loaded and the async workflow explanation is well organized into paragraphs. There is mild redundancy — the immediate-return snapshot is described in paragraph two while paragraph three re-explains pendingReason states, and the urn/null detail reads as return-value documentation.

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 carries the burden of return values and does so (company urn, member urns, nullability, status envelopes), and it fully covers the async lifecycle. It omits what 'basic information' concretely contains and any note on result size limits for retrieved employees/decision makers, but otherwise an agent has what it needs to call and follow up 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 description coverage is 100% and nested configs (dmsRetrievalConfig, employeesRetrievalConfig with filters) are fully documented in the schema, so the baseline of 3 applies. The description only echoes the optional employees/decision-makers capability and adds no parameter syntax or constraint detail 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?

States a specific verb and resource ('open a company page in Sales Navigator to retrieve its basic information') plus the optional employee/decision-maker retrieval, and names the underlying action nv.openCompanyPage. It is clearly distinguishable from search-oriented siblings like nv_search_companies, though it never explicitly contrasts itself with the similarly named fetch_company.

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 strong operational guidance: call get_workflow_result with the returned workflowId/operationName, do not retry the original tool while a workflow is running, and report the working-hours window to the user rather than looping. It does not, however, say when to choose this tool over nv_search_companies or fetch_company, so alternative selection is left implicit.

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.