Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

tiktok_mobile_comment_replies

Retrieve replies to a TikTok comment by video and comment ID; returns cursor, has_more, and total, working even when top-level comment lists are degraded.

Instructions

Retrieve replies to a TikTok comment. Returns the replies to one comment as the mobile app returns them, with cursor, has_more and total. The measured call sends both the video id and the comment id; this route answers even in windows where the top-level comment list is degraded.

Input Schema

NameRequiredDescriptionDefault
countNoReplies per page (max 50)
cursorNoPagination cursor
aweme_idYesVideo id the comment belongs to
comment_idYesComment id to list replies for

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does a decent job: it discloses the pagination envelope (`cursor`, `has_more`, `total`) and a concrete behavioral trait — this route keeps working when the top-level comment list is degraded. It omits auth/rate-limit context, which keeps it short of a 5.

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?

Three sentences, front-loaded with the action, followed by return shape and a reliability caveat. No filler, though the 'as the mobile app returns them' phrasing is slightly redundant with the tool's own mobile naming.

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 naming the returned fields and pagination behavior. For a four-param read tool with full schema coverage, this is complete enough; only the dependency on obtaining a comment id first is left implicit.

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 baseline is 3. The description restates that both video id and comment id are sent ('the measured call sends both the video id and the comment id'), confirming the two required params, but adds nothing about `count` or `cursor` handling beyond what the schema already documents.

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+resource: 'Retrieve replies to a TikTok comment'. This implicitly separates it from the video-level `tiktok_mobile_comments` sibling, but it never names that sibling, so the agent must infer the boundary. Purpose is unambiguous otherwise.

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 note about the route answering 'even in windows where the top-level comment list is degraded' hints at reliability trade-offs vs. the comment-list tool, but there is no explicit 'use X when...' or a statement that a `comment_id` must first be obtained from `tiktok_mobile_comments`.

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