Skip to main content
Glama

List comments

list_comments
Read-onlyIdempotent

List comments for a live FastDrop product by its slug, as a two-level tree (top-level comments and their replies). Removed comments appear as a {deleted: true} tombstone. Unauthenticated - available to any agent.

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": {
      "slug": "<slug>"
    },
    "name": "list_comments"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesProduct slug
limitNoMax top-level results, 1-50, default 20

Output Schema

NameRequiredDescriptionDefault
commentsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds genuinely new behavior: results come back as a nested two-level tree and removed comments surface as a {deleted: true} tombstone rather than disappearing, plus the access precondition ('Unauthenticated - available to any agent'). Pagination or ordering behavior is still unstated.

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, front-loaded with the core action and scope, then return shape, then access model. Nothing is redundant and no sentence could be dropped without losing information.

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?

The tool is simple (one required param, an output schema that covers return values), so the description only needs scope, shape, and access, all of which it supplies. The tombstone note covers the one semantic wrinkle an output schema would not make obvious.

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 both slug and limit are already documented in the schema, and the description adds no new syntax or format detail for either. The phrase 'by its slug' merely restates the required parameter, and the tree wording is consistent with the schema's 'Max top-level results' note rather than expanding on it.

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 names a specific verb and resource ('List comments for a live FastDrop product by its slug') and adds the result shape ('two-level tree'), so an agent immediately knows what the tool returns. It never explicitly contrasts itself with nearby siblings such as list_reviews or get_engagement_feed, which is the only thing keeping it from 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 Guidelines3/5

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

Usage is implied by the scope constraint ('live FastDrop product'), which tells the agent this only works for active products. There is no when-to-use/when-not guidance and no named alternative for fetching comment-like data, so the agent must infer routing from the sibling names alone.

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