Skip to main content
Glama

Read team comments on a post

clipember_list_post_comments
Read-onlyIdempotent

Read the internal comments your team left on a post group (groupId from clipember_list_scheduled_posts), oldest first, with author and time. Clients on a preview link never see these.

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": {
      "groupId": "<groupId>"
    },
    "name": "clipember_list_post_comments"
  }
}

Input Schema

NameRequiredDescriptionDefault
groupIdYesThe groupId of the post

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description still adds real behavior: output is ordered oldest first, each comment carries author and time, and the data is team-only ('Clients on a preview link never see these'), which is a visibility rule no annotation encodes.

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?

One dense sentence with the resource and ordering front-loaded, then the id provenance, then the visibility caveat as a short trailing sentence. Nothing is redundant with the title or schema.

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?

For a single-parameter read tool with full annotation coverage and no output schema, the description supplies everything needed: what is returned (author, time), in what order, where the id comes from, and who cannot see the data.

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% and the only parameter is described as 'The groupId of the post', so the baseline is already met. The description goes further by telling the agent where to obtain a valid groupId, which the schema's UUID pattern cannot convey.

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 and resource ('Read the internal comments your team left on a post group'), scopes it to team-internal comments, and specifies ordering ('oldest first'). The visibility caveat about preview-link clients further separates this from client-facing surfaces and from the sibling write tool clipember_add_post_comment.

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?

Gives the concrete prerequisite for using it by naming the source of the required id ('groupId from clipember_list_scheduled_posts'), so the agent knows which tool feeds this one. It does not state when to prefer this over other comment or approval-related siblings, so it stops short of full when/when-not guidance.

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