Skip to main content
Glama

List the companies a LinkedIn profile follows

linkedin_get_profile_interests_companies
Read-onlyIdempotent

List the companies from the interests section of a LinkedIn member's profile, each with its name, page link, logo and follower count. Page on with the nextStart from the previous response. Read-only: returns public data and changes nothing. Costs 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": {
      "publicId": "<publicId>",
      "count": "<count>"
    },
    "name": "linkedin_get_profile_interests_companies"
  }
}

Input Schema

NameRequiredDescriptionDefault
countYesNumber of results to return (1–100). Defaults to 100.
startNoNumber of results to skip. Defaults to 0.
publicIdYesThe member public identity, or the profile link itself, e.g. "williamhgates" or "https://www.linkedin.com/in/williamhgates".
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
    • changedInput schema / properties / count / default
      Previous value: -10New value: +100
    • changedInput schema / properties / count / description
      Previous value: -"Number of results to return (1–100). Defaults to 10."New value: +"Number of results to return (1–100). Defaults to 100."
  2. 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"
      +}
  3. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description's real added value is the cost model — "Costs 1 credit per request" — plus the note that returned data is public and no state changes. It stops short of describing failure modes (private profile, empty interests) or how credits interact with the cached path.

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 with zero filler: the resource and returned fields come first, then pagination, then the cost/safety profile. Every sentence carries distinct, actionable information.

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 lists the return fields and covers pagination, cost and read-only behavior, while the schema handles caching thoroughly. It is only missing edge-case behavior for profiles without an interests section or insufficient credits.

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 count, start, publicId, cacheOnly and cacheMaxAgeHours are fully documented in the schema and the baseline of 3 applies. The description only touches pagination, and does so via a `nextStart` name that does not match the schema's `start` parameter, which could momentarily confuse an agent mapping the response back to the request.

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 ("List the companies from the interests section of a LinkedIn member's profile") and enumerates the returned fields, which cleanly separates it from the sibling interests tools for groups, newsletters, schools and top voices.

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 description scopes usage to a member's interests section and gives a pagination instruction, but it never says when to prefer this over alternatives such as linkedin_search_companies, nor does it state preconditions or exclusions.

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