Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

tiktok_video_comment_replies

Fetch replies to a TikTok comment using its video URL and comment ID, then use the cursor to retrieve more replies.

Instructions

tiktok: Comment Replies. GET /v1/tiktok/video/comment/replies. Scrapes replies to a TikTok comment Costs 1 credit when it succeeds. Errors, blocked or timed-out requests, invalid requests and cache hits cost nothing. A not-found or empty result is charged only where that operation's published cost says so.

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": {
      "comment_id": "<comment_id>",
      "url": "<url>"
    },
    "name": "tiktok_video_comment_replies"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesTikTok video URL. This is the url from the comments endpoint.
cursorNoCursor to get more replies. Get 'cursor' from previous response.
comment_idYesTikTok comment ID. This is the cid from the comments endpoint.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and delivers a detailed cost model: 1 credit on success, free on errors, blocked/timed-out requests, invalid requests and cache hits. What it does not cover is rate limiting, authentication, or how large a reply page is, so it stops short of full behavioral disclosure for a scraping operation.

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 the resource and endpoint, then the single most decision-relevant fact (cost). The trailing sentence about not-found or empty results is wordy and self-referential ('where that operation's published cost says so') rather than stating the rule directly, which is the only real waste.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Three parameters with no annotations and no output schema, so the description should ideally say what a reply record contains and how cursor pagination terminates. It covers purpose and cost well but leaves the return shape entirely unspecified, which matters for a scraper whose output the agent must parse.

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 coverage is 100% and every parameter (url, comment_id, cursor) already carries a description including examples, so the description adds no parameter meaning of its own. Baseline 3 applies because the schema does all the work.

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 ("Scrapes replies to a TikTok comment") plus the underlying endpoint, which distinguishes it from the sibling tiktok_video_comments that retrieves top-level comments. It never explicitly names that sibling, but the resource is concrete enough to route correctly.

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?

No explicit when-to-use or when-not-to-use guidance; usage is only implied by the schema notes ('This is the cid from the comments endpoint', 'Cursor to get more replies'), which convey a comments-then-replies chaining pattern. An agent can infer the workflow but the description itself gives no prerequisites or alternatives.

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