Skip to main content
Glama

SourceGeek

Get post comments by URL

employee_post_comments_by_share_url
Read-only

List comments on a public post identified by its share URL: text, author, created date, reaction counts. Sort mostRelevant or mostRecent; paged.

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": {
      "shareUrl": "<shareUrl>"
    },
    "name": "employee_post_comments_by_share_url"
  }
}

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.
shareUrlYesThe post's share URL (a /posts/… URL).
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.6/5.0
Behavior3/5

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

Annotations already declare read-only, non-destructive, open-world access, so the safety profile is covered. The description adds meaningful context the annotations lack: it discloses the returned fields (text, author, created date, reaction counts) and notes that results are paged, but says nothing about rate limits, whether comments can be hidden/deleted, or how deep pagination goes.

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, with the resource and its URL-based identification front-loaded before the sort/paging detail. Every clause carries information.

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?

There is no output schema, and the description compensates by enumerating the returned fields and noting pagination. Given five parameters fully covered by schema descriptions and annotations carrying the safety profile, the definition is essentially complete; only page-size/depth behavior and error cases go unstated.

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%, and every schema property is already documented with defaults and bounds. The description only restates the sort enum values and the paging concept, adding no new meaning beyond the schema, so the 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?

The description states a specific verb and resource ('List comments on a public post') plus the identifying key ('share URL'), which lets an agent separate it from sibling tools like employee_post_comments. It stops short of naming an alternative outright, so differentiation is implied by the URL-based lookup rather than stated.

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?

'identified by its share URL' implies the selection condition (you have a /posts/… URL rather than an internal post ID), but there is no explicit when-to-use, when-not-to-use, or named alternative. The agent must infer that this is the URL-keyed variant of the comments tool.

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