Skip to main content
Glama

LinkedIn Company Info

linkedin_company_info

[Acquire · 1 credit] Fetch one LinkedIn company (numeric id, name, industry, size, location, website, description). Costs 1 credit per call. Use it to resolve a company to its numeric LinkedIn id, which linkedin_people_search (company) and linkedin_job_search (companyId) take for an exact company match. Look up by linkedin_url when you have it: a lookup by name returns the best match, which can be a different company with a similar name. The company is saved to companies.

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

Input Schema

NameRequiredDescriptionDefault
nameNoCompany name (e.g. 'Acme Analytics'). Returns the best match; check the returned name and URL.
refreshNoBypass the cache and fetch a fresh copy from LinkedIn (costs 1 credit). Default false: a previously-fetched result is returned free, with how long ago it was retrieved.
linkedin_urlNoLinkedIn company URL (e.g. https://www.linkedin.com/company/acme). Most reliable.
universal_nameNoThe slug from the company URL (e.g. 'acme' for linkedin.com/company/acme).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the annotations (openWorldHint, readOnlyHint=false, idempotentHint=false), the description discloses the credit cost per call and the persistence side effect ('The company is saved to `companies`'), which explains why the call is not read-only. That is exactly the kind of context the annotations alone 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?

Four sentences, front-loaded with the credit cost and the core action, then the resolution purpose and the lookup preference. Minor redundancy between '[Acquire · 1 credit]' and 'Costs 1 credit per call' costs it the top mark.

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 usefully enumerates the returned fields, and it covers cost, caching implications, and the persistence side effect. It does not state what happens when no match is found or whether a failed lookup still consumes a credit, which is the remaining gap for a paid external lookup.

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%, and the schema already documents each parameter, including the 'best match' caveat for `name` and 'Most reliable' for `linkedin_url`. The description largely restates that priority rather than adding new syntax or constraints, so the baseline of 3 is appropriate.

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

Purpose5/5

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

States a specific verb and resource ('Fetch one LinkedIn company') and enumerates the returned fields (numeric id, name, industry, size, location, website, description). It also positions the tool in the workflow by naming the siblings that consume its output (linkedin_people_search `company`, linkedin_job_search `companyId`), so an agent can tell it apart from the other LinkedIn tools.

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 a clear reason to call it (resolve a company to its numeric id for exact-match searches) and a concrete preference rule: use `linkedin_url` when available because name lookup may return a different company with a similar name. It does not explicitly say when to prefer linkedin_company_search over this tool, but the usage context is otherwise unambiguous.

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.