Skip to main content
Glama

List comments

list_comments
Read-only

List the comments on one Instagram, Facebook, TikTok or YouTube post, with the account's recent posts. Omit postId for the newest post. Replies carry parentId. On TikTok and YouTube, pass nextCursor back as cursor for the next page. YouTube comments held for review are listed with isHidden true. TikTok comments are refreshed from TikTok at most every 10 minutes per post, so do not re-read to check for new ones.

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

Input Schema

NameRequiredDescriptionDefault
cursorNo
postIdNo
platformYes
accountIdYesAn accountId from list_accounts.
profileIdNoA profileId from list_profiles. Optional when accountId is given, which names its profile; if both are given they must agree.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / profileId / description
      Previous value: -"Defaults to the profile your API key is bound to."New value: +"A profileId from list_profiles. Optional when accountId is given, which names its profile; if both are given they must agree."
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, and the description adds non-obvious behavior: replies carry parentId, YouTube held-for-review comments appear with isHidden=true, and TikTok comments refresh at most every 10 minutes per post. These details materially help an agent interpret results and avoid unnecessary calls.

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?

The description is five tight sentences, front-loaded with scope and then operational caveats. Every sentence adds useful information with no filler.

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?

With no output schema, the description still covers pagination, hidden comments, reply linkage, and refresh limits, which is enough to call the tool correctly. It does not sketch the returned comment fields beyond parentId and isHidden, so it is not fully complete for result interpretation.

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 description coverage is only 40%, but the description compensates by explaining postId omission and cursor pagination semantics, and by naming the supported platform set. accountId and profileId are already documented in the schema, leaving only a minor gap.

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, 'List the comments,' scoped to one post across four named platforms. It clearly distinguishes read-only comment listing from sibling operations like reply_to_comment, update_comment, and delete_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 concrete operational guidance: omit postId for the newest post, pass nextCursor back as cursor on TikTok/YouTube, and avoid re-reading TikTok comments within 10 minutes. It does not explicitly route agents to list_posts for finding a postId or to reply_to_comment for responses, 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