Skip to main content
Glama

LinkedIn Profile Reactions

linkedin_profile_reactions

[Acquire · 5 credits] Fetch the recent posts a LinkedIn person has reacted to. Useful for inferring interests. Costs 5 credits per call.

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": {
      "linkedin_url": "<linkedin_url>"
    },
    "name": "linkedin_profile_reactions"
  }
}

Input Schema

NameRequiredDescriptionDefault
refreshNoBypass the cache and re-fetch from LinkedIn (costs 5 credits). Default false: a previously-fetched result is returned free, with how long ago it was retrieved.
linkedin_urlYesLinkedIn profile URL of the person whose reactions you want

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare openWorldHint=true, non-idempotent, non-destructive; the description adds the key trait they do not carry — a 5-credit charge per call. It does not disclose result volume or how far back "recent" extends, but the pricing disclosure is genuinely useful added context.

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?

Three short sentences, cost front-loaded in a bracketed tag. Minor redundancy: the 5-credit cost is stated twice (tag and closing sentence), which is the only wasted text.

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

Completeness3/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 leaves the returned shape undefined — how many posts, what fields, and what window "recent" covers are all unstated. The cost and cache behavior are covered, so it is adequate but not complete for a paid, open-world fetch.

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%, and the schema itself fully explains the refresh/cache trade-off and costs. The description mentions neither parameter, so it adds no meaning beyond the schema; baseline 3 applies since the schema does the work.

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?

"Fetch the recent posts a LinkedIn person has reacted to" gives a specific verb (fetch) and a precisely scoped resource (posts reacted to by a person), which is distinguishable from a post-level reactions tool or a profile-posts tool. It stops short of naming a sibling to route against, so clarity comes from the resource wording alone.

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?

"Useful for inferring interests" supplies a motivation/context for calling it, which implies usage but gives no when-to-use versus when-not guidance and no named alternative. The cost line informs the decision economically but is not 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.

Resources