Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List TikTok comment replies

tiktok_video_comments_replies_list
Read-onlyIdempotent

Lists replies to a specific TikTok video comment using its comment ID and video URL, with cursor pagination for retrieving additional reply pages.

Instructions

List replies to a TikTok video comment. Requires commentId and url. Returns a list (use cursor when paginated).

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": {
      "commentId": "<commentId>",
      "url": "<url>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "tiktok_video_comments_replies_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesRequired. Link to the TikTok video that contains the parent comment.
cursorNoOpaque cursor from a previous response to fetch the next page.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
commentIdYesParent comment id from List TikTok video comments (`data.comments[].id`).
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is covered. The description adds that a cursor is used for pagination, which is genuinely useful beyond the annotations, but says nothing about rate limits, ordering, or result volume.

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?

Three short sentences, front-loaded with the verb and resource, with no filler. Slight redundancy in restating the required parameters that the schema already enforces.

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 simple read-only paginated list tool with full schema coverage, rich annotations, and no output schema, the description covers what an agent needs: required inputs, pagination mechanism, and return shape.

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 the schema already fully documents all six parameters including cursor and commentId. The description merely restates that commentId and url are required plus a hint to use the cursor when paginated, adding marginal meaning beyond the schema baseline.

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?

States a specific verb and resource: listing replies to a TikTok video comment, which is distinguishable from the sibling that lists top-level comments (tiktok_video_comments_list). It does not explicitly name that sibling, so the differentiation relies on the agent inferring 'replies' vs 'comments' semantics.

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?

Conveys the prerequisite condition for use (a parent commentId plus the video url), which implicitly frames it as the follow-up to a comments list call. It offers no explicit when-not guidance or named alternative for retrieving the parent comments themselves.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools