Skip to main content
Glama

Get post review comments

get_post_comments

Read-only. Comments left during approval of one post (change requests and approval notes), oldest first, so you can see what the reviewer asked for. Not the scheduled first comment. The agent cannot write or reply to review comments.

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": {
      "id": "<id>"
    },
    "name": "get_post_comments"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe post id.
limitNoPage size, default 20.
offsetNoItems to skip, default 0.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description must carry the safety profile, and it does: 'Read-only' and 'The agent cannot write or reply to review comments' disclose the capability boundary, and 'oldest first' discloses result ordering. It does not say what happens when a post has no approval comments, whether resolved/outdated comments are included, or how pagination exhaustion behaves, leaving some behavioral gaps for a tool with zero annotation coverage.

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?

Three short sentences with zero filler: the read-only constraint leads, the scope and ordering follow, and the capability limit closes. Every sentence earns its place.

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 does convey what the returned items are (change requests and approval notes) and their ordering. It stops short of describing the shape of a comment (author, timestamp, resolved state) or the empty/error case, which an agent would need to interpret results fully.

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 all three parameters (id, limit, offset) are documented in the schema, so the baseline is 3. The description adds only indirect meaning by noting 'oldest first', which implies the order in which offset/limit traverse the collection, but it adds no detail beyond that.

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 the specific resource (comments left during approval of one post), the content types returned (change requests and approval notes), and the ordering (oldest first). It also pre-empts confusion with the post's scheduled first comment, which distinguishes it from get_post. The only gap is the absence of an explicit verb like 'list' or 'fetch', which makes it marginally less crisp than a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a clear context for use: 'so you can see what the reviewer asked for', i.e., inspect approval feedback on a specific post. It also excludes a likely confusion point ('Not the scheduled first comment') and states the agent cannot write or reply. It does not name a sibling alternative by name (e.g., get_approval_status), so the routing guidance is strong but not exhaustive.

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