Skip to main content
Glama

Comments on the posts

list_comments
Read-onlyIdempotent

What people wrote under the artist's posted Promo posts, read live from Instagram and YouTube, newest first, each with its comment_id, who wrote it (from_you when the artist's own account did), when, its likes and its first replies. Without post_id: the comments on the latest posted posts, 5 posts at a time (posts_offset for older ones). With post_id: that post's comments page by page (cursor). networks says which connected networks cannot be read and why: Meta refused Audora the permission to read Facebook comments, and TikTok's API has no way to read them. Reply with reply_comment.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_comments"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoComments per post, 1–50. Default 20 on one post, 10 each otherwise.
postsNoWithout post_id: how many posts, 1–10. Default 5.
artistNoOnly when you are connected as a label: the roster artist this call is for — their artist_user_id from list_roster, or their exact artist name. Required for every artist tool on a label connection. Leave it out on an artist's own connection.
cursorNoWith post_id: next_cursor from the last call, for the next page of its comments.
post_idNoOne posted post (post_id from this tool, promo_results or get_campaign).
posts_offsetNoWithout post_id: skip this many of the latest posts (next_posts_offset).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered; the description adds genuinely new behavior — data is read live from Instagram and YouTube, results are newest-first, pagination differs per mode, and unreadable networks are surfaced with reasons (Meta permission refusal, TikTok API limitation). It does not explain what happens when no posts exist or how a partially failing network affects the rest of the response, which keeps it short of a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with what the tool returns, then the two modes, then the network caveat, then the sibling pointer — no wasted sentences. It is a single dense block, though, and the 'networks' clause sits in the middle of what reads like parameter guidance even though networks is a response field, which slightly muddies scanning.

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?

With no output schema, the description carries the return-value burden itself and does so: comment_id, author identity including the from_you flag, timestamp, likes, first replies, plus the networks diagnostic field. Pagination, defaults and the label-vs-artist connection context are all handled by the schema, so nothing an agent needs is missing.

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%, so baseline is 3; the description earns an extra point by explaining the dependency structure between post_id, posts_offset and cursor rather than restating each parameter in isolation. Limit's dual default (20 on one post, 10 each otherwise) is left entirely to the schema, which slightly limits the added value.

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 ('what people wrote under the artist's posted Promo posts'), names the source networks, the ordering (newest first), and the per-item fields returned. An agent immediately knows this is a read of comments, not posts, and the closing pointer to reply_comment separates it from the write-side sibling.

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

Usage Guidelines5/5

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

Explicitly branches usage by mode: without post_id it walks the latest posted posts five at a time, with post_id it pages through one post's comments via cursor. It also routes the reply case away to reply_comment, so the when-to-use and which-alternative cases are both covered.

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