Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

tiktok_mobile_comments

Read-only

List top-level comments for a video. This route needs a configured app session. A truly empty body can be a degraded throttle window; recheck before treating it as authoritative.

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>"
    },
    "name": "tiktok_mobile_comments"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNoComments to request, maximum 50.
cursorNoPagination cursor returned by the previous page.
aweme_idYesrequired,TikTok video ID to list comments for.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint. The description adds non-obvious operational behavior: an app-session requirement and the possibility that an empty body reflects a degraded throttle window, which is useful beyond the annotations. It does not detail pagination behavior or return shape, but output schema exists.

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?

Three short sentences, purpose front-loaded, with the operational caveat immediately after. Every sentence carries useful information.

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 read-only, open-world list tool with an output schema and fully described parameters, the description covers the important non-obvious conditions: session requirement and degraded-throttle ambiguity. Pagination could be mentioned but is adequately covered by the cursor schema field.

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 aweme_id, count (max 50), and cursor are already documented in the schema. The description adds only the implicit notion that aweme_id identifies the video, so baseline 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?

States a specific verb ('List'), resource ('top-level comments'), and scope ('for a video'). The word 'top-level' distinguishes it from sibling tiktok_mobile_comment_replies and from broader tiktok_comments.

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?

Gives a prerequisite ('needs a configured app session') and a caution about degraded empty responses, but never says when to choose this over tiktok_comments or tiktok_mobile_comment_replies. Usage is implied rather than explicitly routed.

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

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