Skip to main content
Glama

Search LinkedIn companies

linkedin_search_companies
Read-onlyIdempotent

Find LinkedIn companies by keyword. Each result includes the company name, industry, location, follower count, description, logo and page link. Read-only: returns public data and changes nothing. Costs 1 credit per result returned, with a minimum of 1 credit per request.

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": {
      "keyword": "<keyword>",
      "count": "<count>"
    },
    "name": "linkedin_search_companies"
  }
}

Input Schema

NameRequiredDescriptionDefault
countYesNumber of results to return (1–10). Defaults to 10.
startNoNumber of results to skip. Defaults to 0.
keywordYesKeyword(s) to search LinkedIn for, e.g. "openai", "software engineer", "fintech".
cacheOnlyNoReturn only a cached result and never scrape live. With `cacheMaxAgeHours`, only a result that recent is returned; without it, the latest cached result of any age. Responds 404, at no cost, when there is none, e.g. true.
cacheMaxAgeHoursNoAccept a cached result scraped up to this many hours ago. A cached result costs no credits, and its `cachedAt` says when it was scraped. When no cached result is that recent, the data is scraped live at the normal price. Leave it out to always scrape live, e.g. 24.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / cacheMaxAgeHours
      Added value: +{
      +  "description": "Accept a cached result scraped up to this many hours ago. A cached result costs no credits, and its `cachedAt` says when it was scraped. When no cached result is that recent, the data is scraped live at the normal price. Leave it out to always scrape live, e.g. 24.",
      +  "exclusiveMinimum": 0,
      +  "maximum": 9007199254740991,
      +  "type": "integer"
      +}
    • addedInput schema / properties / cacheOnly
      Added value: +{
      +  "description": "Return only a cached result and never scrape live. With `cacheMaxAgeHours`, only a result that recent is returned; without it, the latest cached result of any age. Responds 404, at no cost, when there is none, e.g. true.",
      +  "type": "boolean"
      +}
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the bar is lower, yet the description still adds real value: an explicit cost model (1 credit per result, minimum 1 per request) that an agent needs for budgeting. It falls short of the schema's own caching nuance, which states that cache hits cost nothing.

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

Conciseness5/5

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

Three tight sentences: purpose first, then output shape, then safety and cost. No filler, and the credit cost is placed where an agent will see it before calling.

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 five-parameter search tool with no output schema, listing the returned fields substitutes well for a return-value spec, and the credit note covers the main non-obvious risk. What is missing is guidance on pagination via start and the free cache path, which matter for repeated calls.

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 count, start, keyword, cacheOnly and cacheMaxAgeHours all documented in-schema, so the baseline of 3 applies. The description adds no syntax, default or format guidance beyond what the schema already carries.

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 ('Find LinkedIn companies by keyword') and enumerates the returned fields. It does not, however, distinguish itself from the very similar sibling linkedin_search_all or contrast with linkedin_get_company_from_url, which handles URL-based lookup.

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 keyword-based framing implies you use this when you have a search term rather than a company URL or slug, but the description never states when to prefer linkedin_get_company_from_url or linkedin_search_all. Usage is inferable from the siblings' names, not from the text.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources