Fresh Linkedin Profile Data MCP Server

Get Companies

get_companies

Retrieve LinkedIn company records from search results using a request ID and optional page number to access paginated data.

Instructions

Get search results. Please make sure the search is \

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": {
      "request_id": "<request_id>"
    },
    "name": "get_companies"
  }
}

Input Schema

Name	Required	Description	Default
`page`	No	Example value: 1
`request_id`	Yes	Example value: ba072fac0b38d12378ef5023742f0184s34e1i8n2a7p0m9o

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Sep 4, 2026

TDQS

D1.8/5.0

Behavior1/5

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

With no annotations, the description carries the full burden of behavioral disclosure, and it discloses almost nothing beyond the vague fact that it returns search results. There is no mention of pagination, request_id handling, search lifecycle, or possible errors, and the truncated sentence gives misleading or unparseable behavioral guidance.

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

Conciseness1/5

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

The description is short but structurally broken: "Please make sure the search is \"" is an incomplete, malformed sentence that provides no value. There is no front-loaded clarity, and the text appears truncated, making it unusable as a concise definition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with two parameters, no output schema, and many closely related siblings, this description is drastically incomplete. It fails to explain how request_id relates to a company search, whether results are paginated, how to interpret the response, or how this tool differs from the many sibling search tools.

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 baseline is 3 even though the description adds no real parameter insight. The description's incomplete reference to "the search" does not clarify request_id or page, but the schema at least documents both parameters with example values.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description says only "Get search results," which is vague and fails to identify companies as the resource, especially with the sibling get_search_results present. The truncated sentence adds confusion rather than clarity, and the description does not distinguish this tool from get_company_by_id, get_company_by_url, or search_companies.

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

Usage Guidelines2/5

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

No usage context is provided: there is no indication of when to use get_companies versus get_search_results, search_companies, or check_company_search_status. The partial instruction "Please make sure the search is \"" is incomplete and offers no actionable guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server