Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

tiktok_video_comments

Retrieves comments from public TikTok videos and slideshows using a URL, with cursor pagination for more results. Use it to collect viewer responses from a specific post.

Instructions

tiktok: Comments. GET /v1/tiktok/video/comments. Get comments on public TikTok videos or slideshows. Pages with comments cost 1 credit; empty pages cost 0. An empty page does not prove the post has no comments globally. Costs 1 credit when it succeeds. Costs 0 credits when comments is empty. 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": {
      "url": "<url>"
    },
    "name": "tiktok_video_comments"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesTikTok video URL
trimNoSet to true to get a trimmed response
cursorNoCursor to get more comments. Get 'cursor' from previous response.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/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 does disclose meaningful behavior: pagination costs 1 credit per non-empty page, empty pages and errors/blocked/timed-out/invalid/cached calls cost 0, and — importantly — an empty page does not prove the post has no comments globally. It omits other behavioral traits such as ordering of comments, rate limits, or what a trimmed response contains.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and the key caveat (empty page ≠ no comments) are front-loaded and useful. However, the cost model is restated three times in slightly different wording ("Pages with comments cost 1 credit; empty pages cost 0", then "Costs 1 credit when it succeeds. Costs 0 credits when comments is empty", then the error/cache sentence), which is redundant padding.

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?

For a 3-parameter, no-annotation, no-output-schema tool, the definition covers cost semantics well but leaves gaps: it does not describe the shape of the returned comment data, how pagination terminates, or what trim changes. Adequate to invoke correctly, but not complete.

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 url, trim, and cursor are already documented in the schema; baseline 3 applies. The description's repeated mention of "pages" and "empty pages" loosely reinforces the cursor pagination model but adds no syntax, default, or meaning for trim beyond what the schema says.

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 ("Get comments on public TikTok videos or slideshows") plus the underlying route GET /v1/tiktok/video/comments, so the agent knows exactly what it retrieves. It does not distinguish itself from the sibling tiktok_video_comment_replies, leaving the comments-vs-replies boundary to be inferred from names alone.

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?

Usage is only implied: the tool takes a TikTok video URL, so the agent infers it applies to public TikTok videos. There is no explicit when-to-use statement, no prerequisite (e.g. public vs private accounts), and no named alternative for related needs like replies or transcripts. The bulk of the text is pricing rather than selection 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