Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List TikTok video comments

tiktok_video_comments_list
Read-onlyIdempotent

List comments on a TikTok video by passing its URL; use the returned cursor to page through additional comments.

Instructions

List comments on a TikTok video by URL. Requires url. Returns a list (use cursor when paginated). Pass the video link or numeric video id in url; there is no videoId field.

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

Input Schema

NameRequiredDescriptionDefault
urlYesRequired. Link to the TikTok video whose comments should be listed.
trimNoWhen true, returns a smaller response with fewer fields.
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.
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.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 and open-world, so safety is covered; the description goes beyond them by disclosing the paginated list response and the cursor-based continuation behavior. It also preempts a likely invocation error by ruling out a videoId field, though it says nothing about rate limits or response size beyond the `trim` parameter.

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 with the core action and required parameter first, then return shape, then the parameter gotcha. Every sentence carries information an agent would otherwise have to guess.

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?

For a six-parameter read-only list tool with no output schema, the description covers action, required input, accepted input formats, and pagination. The plumbing parameters (context, llm_model, conversation_id) are handled entirely by rich schema descriptions, so nothing critical is missing, though the description could mention the conversation_id sequencing requirement since it constrains parallel calls.

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 the baseline is 3, and the description earns above that by clarifying that `url` accepts either a full link or a numeric video id -- meaning the schema's own wording ('Link to the TikTok video') does not convey. The cursor pagination note reinforces the opaque-cursor semantics. It says nothing about trim/context/llm_model, but those are fully documented in the schema.

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 (list comments) plus the platform (TikTok video), which cleanly separates it from the likes/related/subtitles siblings and from the replies variant. It does not explicitly name tiktok_video_comments_replies_list as the place for nested replies, so sibling routing is implied rather than spelled out.

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?

Gives a concrete calling constraint ('Pass the video link or numeric video id in `url`; there is no videoId field') and a follow-up mechanic ('use cursor when paginated'), which is real usage guidance. It never states when to prefer this over tiktok_video_comments_replies_list or the analogous YouTube/Vimeo comment tools, so there is no when-not guidance.

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