Linked API

nv_search_companies

Read-only

Allows you to search for companies in Sales Navigator applying various filtering criteria. (nv.searchCompanies action). Every company in the result carries urn — its permanent LinkedIn organization URN (urn:li:organization:), or null when LinkedIn does not expose it.

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

Input Schema

Name	Required	Description
`term`	No	Optional. Keyword or phrase to search.
`limit`	No	Optional. Number of search results to return. Defaults to 25, with a maximum value of 1000.
`filter`	No	Optional. Object that specifies filtering criteria for companies. When multiple filter fields are specified, they are combined using AND logic.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 29, 2026

TDQS

A3.9/5.0

Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint; the description supplies the behavior that actually matters here — that actions are queued into a cloud-browser workflow, may take minutes, and return an immediate pending/running snapshot rather than results. It also decodes pendingReason 'queued' and 'outsideWorkingHours', explaining that the latter can park work until the next working day and that get_workflow_result will return immediately rather than poll.

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 in the first sentence, and the async mechanics follow in logical order with the escalation path (pending → get_workflow_result) spelled out. The urn sentence is a non-sequitur wedged between the purpose and the workflow explanation, and the outsideWorkingHours paragraph is long, but nearly every sentence carries operational weight.

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 correctly takes on the burden of explaining the immediate return shape (status, pendingReason, workflowId, operationName, message) and how to get the final result, which is exactly the gap an agent would otherwise fall into. It is less complete on the domain side: it doesn't say what company fields come back beyond urn, nor how this differs from `search_companies`.

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%, so the schema already documents `term`, `limit`, the `filter` object, and the AND-combination semantics, making 3 the baseline. The description adds no parameter-level meaning beyond the schema; the one substantive detail it offers (urn presence on results) describes output, not inputs.

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 specific verb and resource ('search for companies in Sales Navigator') and names the underlying action (nv.searchCompanies), which is clear enough to act on. However, it never distinguishes itself from the sibling `search_companies`, which appears to do the same thing outside Sales Navigator, so an agent can't tell from the description alone which one to pick.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The guidance is strong on the async workflow: call `get_workflow_result` with the returned workflowId/operationName, and do not retry the original tool while a workflow is running to avoid duplicate queued work. What's missing is the selection-level guidance — when to use this over `search_companies` or `fetch_company` — which is the more consequential ambiguity given the sibling list.

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.