Skip to main content
Glama

LinkedIn: list mentionable people

linkedin_list_mentionables
Read-onlyIdempotent

List LinkedIn people captured from engagement (comments/reactions) on your connected company pages. Pass the selected channel platformId to use its current application identity. Each entry carries the native app-scoped person id — the only id namespace LinkedIn resolves in mentions — plus a ready-to-use mention token in the form @{urn:li:person:ID|Name}. Requires a paid plan (403 UPGRADE_REQUIRED otherwise).

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_list_mentionables"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoName filter (substring)
limitNoMax results (default 25)
platformIdNoSelected channel ID from list_connections, for application-correct person IDs.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / platformId
      Added value: +{
      +  "description": "Selected channel ID from list_connections, for application-correct person IDs.",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover read-only/idempotent/non-destructive, and the description adds behavior they cannot express: plan gating with the specific error code 403 UPGRADE_REQUIRED, the fact that only app-scoped person ids resolve in mentions, and the mention token format returned per entry. This is exactly the kind of context that prevents failed calls downstream.

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, each carrying distinct information, with the core purpose front-loaded before the identity/format detail. The third sentence is long and dense with jargon (id namespace, urn token syntax), which costs some readability but no sentence is filler.

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

Completeness5/5

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

There is no output schema, and the description compensates by describing exactly what each entry contains (app-scoped person id plus a ready-to-use mention token in @{urn:li:person:ID|Name} form). Combined with the plan-gating caveat, an agent has everything needed to call and consume the result correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so q and limit are already documented and the baseline is 3. The description adds real meaning for platformId by explaining it selects the current application identity and yields application-correct person ids — semantics the schema's 'Selected channel ID' text only hints at.

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?

The first sentence states a specific verb and resource ('List LinkedIn people') and pins down the exact data source ('captured from engagement (comments/reactions) on your connected company pages'), which is what separates it from generic people/connection tools like list_connections. An agent can tell what it returns without opening the schema.

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?

It gives a concrete usage rule ('Pass the selected channel platformId to use its current application identity') and a precondition ('Requires a paid plan (403 UPGRADE_REQUIRED otherwise)'). It does not name an alternative tool or say when not to use it, e.g. when to prefer list_connections instead, so it falls short of explicit routing guidance.

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.