Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

tiktok_comments

Fetch top-level comments for a TikTok video by aweme_id. Paginate with cursor, check has_more, and read total count.

Instructions

Retrieve TikTok video comments. Returns the top-level comments on a TikTok video, by the video id from its URL (aweme_id). Results are paged by cursor: pass the cursor from one response to get the next page, and read has_more to see whether more remain. The response also carries the total comment count.

Input Schema

NameRequiredDescriptionDefault
cursorNoPagination cursor
aweme_idYesTikTok video id from the video URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.0

TDQS

A4.4/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 well: it discloses that only top-level comments are returned (not replies), that results are cursor-paged, that has_more signals continuation, and that a total comment count accompanies the response. It omits ordering, page size, and any auth/rate-limit 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?

Four tight sentences, front-loaded with the purpose and scope before pagination mechanics. No filler and nothing repeated from the schema verbatim.

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?

No output schema exists, and the description compensates by describing the return payload shape (comments, pagination cursor, has_more, total count). Minor gaps remain around ordering and whether the total count includes replies, but an agent has everything needed to call and iterate correctly.

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 already 100%, so the baseline is 3, but the description adds real meaning: aweme_id is sourced from the video URL, and cursor is fed forward from a previous response rather than being an arbitrary value. It also introduces has_more, which is not a parameter but frames the pagination loop.

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?

States a specific verb and resource ('Retrieve TikTok video comments') and narrows the scope to 'top-level comments on a TikTok video' keyed by aweme_id. An agent can distinguish this from tiktok_post or youtube_comments without opening any schema.

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?

Gives clear invocation context: identify the video by the id taken from its URL, and page through results using the cursor from the prior response. It does not name an alternative tool or state when not to use this one, so it stops short of a 5.

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