Skip to main content
Glama

LinkedIn Post Comments

linkedin_post_comments

[Acquire · 1 credit/page] Fetch the people who commented on a single LinkedIn post (and their comment text), including replies to comments. Costs 1 credit per page of up to 100 comments, walking up to max_pages pages (default 10), so at most max_pages credits; cached pages are free. The output's fetched / total_available / truncated fields say when the post had more comments than were fetched. Each comment and reply is persisted to post_engagements with the commenter and full comment text.

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": {
      "post_url": "<post_url>"
    },
    "name": "linkedin_post_comments"
  }
}

Input Schema

NameRequiredDescriptionDefault
refreshNoBypass the cache and re-fetch from LinkedIn (costs 1 credit per page). Default false: previously-fetched pages are returned free, with how long ago they were retrieved.
post_urlYesPublic LinkedIn post URL (e.g. https://www.linkedin.com/feed/update/urn:li:activity:1234)
max_pagesNoMax pages of up to 100 comments to fetch (1-20, default 10). Each page costs 1 credit.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / max_pages
      Added value: +{
      +  "description": "Max pages of up to 100 comments to fetch (1-20, default 10). Each page costs 1 credit.",
      +  "maximum": 20,
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • changedInput schema / properties / refresh / description
      Previous value: -"Bypass 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."New value: +"Bypass the cache and re-fetch from LinkedIn (costs 1 credit per page). Default false: previously-fetched pages are returned free, with how long ago they were retrieved."
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already flag openWorldHint=true and readOnlyHint=false; the description adds the crucial missing context that each comment and reply is persisted to post_engagements, which explains the non-read-only hint. It also discloses per-page credit cost, the max_pages credit ceiling, and that cached pages are free. It stops short of describing rate limits or failure modes, so a 4 rather than a 5.

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?

Cost and scope are front-loaded in a bracketed tag followed by a single dense but well-ordered block covering what it fetches, what it costs, truncation signaling, and persistence. No filler sentences, though the cost explanation is repeated enough that it could be tightened slightly.

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?

With no output schema, the description still names the relevant return fields (fetched, total_available, truncated) so an agent understands truncation reporting. Combined with the side-effect disclosure (post_engagements persistence) and the credit model, nothing essential for calling this tool correctly is missing.

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 the baseline is 3, but the description adds cost semantics that the schema does not state: total spend equals pages walked up to max_pages (default 10), and cached pages incur no charge. That cross-parameter cost model is genuine added meaning.

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 (Fetch) and a precisely scoped resource: the people who commented on a single LinkedIn post, plus their comment text and replies. The 'single post' scoping implicitly separates it from profile-level comment tools and reaction tools without ambiguity.

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?

Usage context is implied by the resource description and the cost framing (credit per page, cache behavior), which helps an agent decide whether to raise max_pages or set refresh. However, there is no explicit when-to-use / when-not-to-use guidance and no named alternative such as linkedin_profile_comments or linkedin_post_reactions for other engagement data.

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