Linked API

search_companies

Read-only

Allows you to search for companies applying various filtering criteria (st.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": "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 10, 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

A4.1/5.0

Behavior5/5

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

The description goes well beyond readOnlyHint/openWorldHint by disclosing that actions are queued into a cloud-browser workflow, that the call returns immediately with a pending/running envelope, the meaning of pendingReason 'queued' vs 'outsideWorkingHours', and the duplicate-work hazard of retrying. It also discloses a result nuance (urn may be null when LinkedIn does not expose it) that no annotation conveys.

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, followed by output-envelope and pending-state handling in a logical order. It runs four paragraphs and some of the get_workflow_result polling explanation is generic boilerplate, but each paragraph still carries actionable information for an agent with 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?

With no output schema, the description compensates by documenting the immediate return envelope, the two pendingReason values, and the fact that final results require a follow-up call. The shape of the completed result set (beyond the urn field) is left unstated, but the async contract — the hardest part of this tool — is fully covered.

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%, including the nested filter object and its AND-combination semantics, so the schema already carries parameter meaning. The description adds nothing about term matching, filter value formats, or how limit interacts with workflows, so the baseline of 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?

The first sentence gives a specific verb and resource ("search for companies applying various filtering criteria") and names the underlying action. It is clear about what the tool does, but it never distinguishes itself from the sibling nv_search_companies, which appears to cover the same resource, so an agent cannot pick between them from the description alone.

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?

Strong operational guidance: call get_workflow_result with the returned workflowId and operationName, do not retry the original tool while a workflow is running, and report the working-hours case to the user instead of looping. What is missing is task-level routing — when to use this versus nv_search_companies or fetch_company for a known organization.

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.