Skip to main content
Glama

LinkedIn Profile Comments

linkedin_profile_comments

[Acquire · 5 credits] Fetch the recent posts a LinkedIn person has commented on. Useful for inferring interests and conversation partners. 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_comments"
  }
}

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 comments you want

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare openWorldHint, non-idempotency and non-read-only status, so the baseline is low; the description adds the one trait annotations cannot express — a metered cost of 5 credits per call, repeated in the header tag. It stops short of describing pagination, result volume, or what happens on credit exhaustion.

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, front-loaded sentences with the cost tag leading, which is the right order for a metered call. Minor waste from stating the 5-credit cost twice (header tag and final sentence).

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 simple two-parameter read/enrich tool with no output schema, the definition covers purpose, motivation, and pricing adequately. A note on roughly how many posts are returned or the shape of the response would close the remaining gap.

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%, including the cache-bypass semantics of 'refresh' and its own credit cost, so the schema does the heavy lifting and the baseline of 3 applies. The description adds no parameter-level meaning beyond restating that comments-URL input is required.

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 description names a specific verb and resource ('Fetch the recent posts a LinkedIn person has commented on') and, by inverting the direction relative to 'comments on a post' and 'posts a person published', an agent can tell it apart from siblings like linkedin_post_comments and linkedin_profile_posts without opening either schema.

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?

It supplies a use-case context ('inferring interests and conversation partners') but no explicit when-to-use branch against the obvious alternatives (profile posts, profile reactions) and no prerequisites or exclusions. Usage is implied rather than guided.

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