captapi

tiktok_comment_replies

Replies under a TikTok comment — same authorId/authorSecUid/commentLanguage shape as comments. Costs 2 credits. Empty results and failures are never charged. Pass cache=true for a free 24h cache hit (default always fresh).

Input Schema

TableJSON Schema

Name	Required	Description
`url`	Yes	Public TikTok video URL, e.g. https://www.tiktok.com/@khaby.lame/video/7646812028874673439. Not a YouTube/Instagram/Facebook URL. The URL platform must match this endpoint's platform. Do not pass cross-platform URLs, e.g. YouTube to TikTok, Instagram to Facebook, LinkedIn to X/Twitter, or Pinterest to Rumble.
`cache`	No	Set true to serve from the 24h response cache (0 credits on hit). Default false — always fetch fresh.
`limit`	No	Max items to return (default 50, max 500). Flat 2 credits per call.
`cursor`	No	Pagination cursor. Leave empty for the first page; then pass the nextCursor value from the previous response.
`commentId`	Yes	ID of the parent (top-level) comment to fetch replies for — from the comments endpoint. Legacy alias: comment_id.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 1, 2026

changedInput schema / properties / cache / description

Previous value: -"Set true to serve from the 24h response cache (0 credits on hit). Default false — always fetch fresh. Envelope includes cached + cachedAt on hits."New value: +"Set true to serve from the 24h response cache (0 credits on hit). Default false — always fetch fresh."

Changed1 schema field changedAug 26, 2026

changedInput schema / properties / url / description

Previous value: -"Public TikTok video URL, e.g. https://tiktok.com/@user/video/ID. Not a YouTube/Instagram/Facebook URL. The URL platform must match this endpoint's platform. Do not pass cross-platform URLs, e.g. YouTube to TikTok, Instagram to Facebook, LinkedIn to X/Twitter, or Pinterest to Rumble."New value: +"Public TikTok video URL, e.g. https://www.tiktok.com/@khaby.lame/video/7646812028874673439. Not a YouTube/Instagram/Facebook URL. The URL platform must match this endpoint's platform. Do not pass cross-platform URLs, e.g. YouTube to TikTok, Instagram to Facebook, LinkedIn to X/Twitter, or Pinterest to Rumble."

Changed5 schema fields changedAug 20, 2026

changedInput schema / properties / cache / description

Previous value: -"Set true to serve from the 24h response cache. Default false — always fetch fresh data."New value: +"Set true to serve from the 24h response cache (0 credits on hit). Default false — always fetch fresh. Envelope includes cached + cachedAt on hits."

changedInput schema / properties / commentId / description

Previous value: -"ID of the parent (top-level) comment to fetch replies for (from the comments endpoint). Legacy alias: comment_id."New value: +"ID of the parent (top-level) comment to fetch replies for — from the comments endpoint. Legacy alias: comment_id."

changedInput schema / properties / cursor / description

Previous value: -"Pagination cursor. Leave empty for the first page; then pass the nextCursor value returned in the previous response."New value: +"Pagination cursor. Leave empty for the first page; then pass the nextCursor value from the previous response."

changedInput schema / properties / limit / description

Previous value: -"Max items to return. Default 50, max 500. Flat 2 credits per call."New value: +"Max items to return (default 50, max 500). Flat 2 credits per call."

changedInput schema / properties / url / description

Previous value: -"Public TikTok video URL, e.g. https://tiktok.com/@user/video/ID. Not a YouTube/Instagram/Facebook URL. The URL platform must match this tool's platform. Do not pass cross-platform URLs, e.g. YouTube to TikTok, Instagram to Facebook, LinkedIn to X/Twitter, or Pinterest to Rumble."New value: +"Public TikTok video URL, e.g. https://tiktok.com/@user/video/ID. Not a YouTube/Instagram/Facebook URL. The URL platform must match this endpoint's platform. Do not pass cross-platform URLs, e.g. YouTube to TikTok, Instagram to Facebook, LinkedIn to X/Twitter, or Pinterest to Rumble."

Changed3 schema fields changedAug 11, 2026

addedInput schema / properties / commentId

Added value: +{
+  "description": "ID of the parent (top-level) comment to fetch replies for (from the comments endpoint). Legacy alias: comment_id.",
+  "type": "string"
+}

removedInput schema / properties / comment_id

Removed value: -{
-  "description": "ID of the parent comment to fetch replies for (from the comments endpoint).",
-  "type": "string"
-}

changedInput schema / required

Previous value: -[
-  "url",
-  "comment_id"
-]New value: +[
+  "url",
+  "commentId"
+]

Changed1 schema field changedJul 18, 2026

changedInput schema / properties / limit / description

Previous value: -"Max items to return. Default 50, max 500. Billed per result."New value: +"Max items to return. Default 50, max 500. Flat 2 credits per call."

Changed1 schema field changedJul 18, 2026

addedInput schema / properties / cursor

Added value: +{
+  "description": "Pagination cursor. Leave empty for the first page; then pass the nextCursor value returned in the previous response.",
+  "type": "string"
+}

Changed1 schema field changedJul 16, 2026

changedInput schema / properties / cache / description

Previous value: -"Responses are cached for 24 hours by default. Set false to bypass the cache and always fetch fresh data (default true)."New value: +"Set true to serve from the 24h response cache. Default false — always fetch fresh data."

Changed1 schema field changedJul 15, 2026

addedInput schema / properties / cache

Added value: +{
+  "description": "Responses are cached for 24 hours by default. Set false to bypass the cache and always fetch fresh data (default true).",
+  "type": "boolean"
+}

Changed1 schema field changedJul 4, 2026

changedInput schema / properties / url / description

Previous value: -"Public TikTok video URL, e.g. https://tiktok.com/@user/video/ID."New value: +"Public TikTok video URL, e.g. https://tiktok.com/@user/video/ID. Not a YouTube/Instagram/Facebook URL. The URL platform must match this tool's platform. Do not pass cross-platform URLs, e.g. YouTube to TikTok, Instagram to Facebook, LinkedIn to X/Twitter, or Pinterest to Rumble."

First observedJun 7, 2026

TDQS

A4.4/5.0

Behavior5/5

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

With no annotations, the description carries the full burden and does it well: it discloses the 2-credit cost, that empty/failed calls are not charged, and the cache=true free-hit behavior with fresh-by-default semantics. It also previews the reply field shape, which is material behavioral context.

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?

Two compact, front-loaded sentences communicate purpose, shape, billing, and cache behavior without filler. Every clause earns its place.

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 5-parameter tool with no output schema and no annotations, the description is quite complete: it covers return shape, cost, failure charging, and cache behavior. It could be slightly more explicit about the full response envelope/pagination metadata, but the schema already documents limit and cursor.

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%, so the schema fully documents all five parameters. The description only restates the cache behavior in pricing terms and does not add meaning beyond the schema, matching the baseline for high schema coverage.

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?

The description names a specific resource ('Replies under a TikTok comment') and a clear retrieval action, distinguishing itself from sibling comment endpoints like tiktok_comments and youtube_comment_replies. It also ties the reply shape to the comments endpoint, removing ambiguity.

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?

The usage context is clear: this tool is for fetching replies on a TikTok comment, and the 'same shape as comments' phrasing points to the related comments endpoint. It lacks an explicit when-not-to-use statement or named alternative, but the intent is not ambiguous.

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

All captapi tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

tiktok_comment_replies

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources