Crawlora MCP

tiktok_mobile_comment_replies

Read-only

List replies to one TikTok comment. This route needs a configured app session; pass both the video ID and comment ID.

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": {
      "aweme_id": "<aweme_id>",
      "comment_id": "<comment_id>"
    },
    "name": "tiktok_mobile_comment_replies"
  }
}

Input Schema

Name	Required	Description
`count`	No	Replies to request, maximum 50.
`cursor`	No	Pagination cursor returned by the previous page.
`aweme_id`	Yes	required,TikTok video ID containing the comment.
`comment_id`	Yes	required,Comment ID whose replies to list.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true. The description adds useful behavioral context beyond that: this route specifically requires a configured app session, which is important for invocation. It does not cover rate limits or return format, but the output schema likely handles the latter.

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?

The description is two short sentences with no wasted language. The core purpose is front-loaded, followed immediately by the session prerequisite and required identifiers.

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 simple listing tool with full schema coverage, output schema, and annotations, the description is largely complete. It covers purpose, session prerequisite, and required IDs; pagination behavior is left to the schema, which is acceptable.

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 description coverage is 100%, so all four parameters are already documented, including count and cursor. The description only restates that video ID and comment ID are required, without adding syntax or meaning beyond the schema, so the baseline of 3 is appropriate.

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 states a specific verb and resource: 'List replies to one TikTok comment.' It clearly scopes the operation to replies of a single comment, which distinguishes it from broader comment-listing siblings such as tiktok_mobile_comments.

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?

It gives a clear usage context by stating the route needs a configured app session and that both the video ID and comment ID must be passed. It does not explicitly name alternatives or when not to use it, but the required inputs and session prerequisite make the intended use clear.

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

All Crawlora MCP 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.

Resources

Need Help?