Skip to main content
Glama

SourceGeek

Get post comments

employee_post_comments
Read-only

List comments on a public post by post urn: text, author (fullName, headline, username, url), created date, reaction and reply counts. Sort mostRelevant or mostRecent; paged via page and paginationToken.

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": {
      "postUrn": "<postUrn>"
    },
    "name": "employee_post_comments"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo1-based results page.
sortNoOrdering; defaults to mostRelevant.
limitNoMaximum items to return (1-100, default 10). Results beyond the provider's page are not fetched.
postUrnYesPost urn / activity id.
paginationTokenNoOpaque token from the previous call's paginationToken; required together with start when fetching the next page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered. The description adds real value beyond that by disclosing the result shape (text, author attributes, created date, reaction and reply counts) and the pagination mechanism — useful since there is no output schema. Auth requirements, rate limits, and whether replies are nested are not covered, keeping it below 5.

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?

Two sentences, zero filler, and the identifying operation is front-loaded before the return fields and the sort/paging options. Every clause carries information an agent can act on.

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 5-parameter read tool with no output schema, the description does the important extra work of listing returned fields and confirming pagination. Remaining gaps are modest: no statement about permissions/public-vs-private access rules beyond "public post", and no note on how limit interacts with the provider page size, though the schema covers the latter.

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 all five parameters are already documented, including enum values and limit bounds. The description only restates the sort options and the two paging parameters, adding no syntax or behavior detail beyond the schema. Baseline 3 applies.

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?

States a specific verb and resource ("List comments on a public post") plus the identifier type ("by post urn"), which implicitly routes the agent away from the share-url sibling. It also enumerates the returned fields, so the agent knows what it gets. It stops short of naming the alternative tool explicitly.

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 is implied rather than stated: "on a public post by post urn" signals the precondition (a post URN, public posts only), and the sort/paging options are described. There is no explicit when-to-use vs. when-to-use-another-tool guidance or any exclusion, so the agent must infer the choice.

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