Crawlora MCP

tiktok_mobile_video_subtitles

Read-only

Retrieve one video's translated subtitle track as WebVTT and parsed cues. Use a supported target-language code: en, ja, zh, es, fr, de, ko, pt, ru, ar, hi, id, th, vi, tr or it.

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": {
      "video_id": "<video_id>",
      "language": "<language>"
    },
    "name": "tiktok_mobile_video_subtitles"
  }
}

Input Schema

Name	Required	Description	Default
`language`	Yes	required,Target language: en, ja, zh, es, fr, de, ko, pt, ru, ar, hi, id, th, vi, tr or it.
`video_id`	Yes	required,Numeric TikTok video ID.

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

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety behavior is covered. The description adds output format and language support, but it does not disclose whether missing translated subtitles cause errors, whether fallback languages exist, or other operational constraints beyond the annotations.

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?

Two sentences are used with no filler: the purpose and return format are front-loaded, and the language list follows immediately as an actionable constraint.

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?

With annotations covering safety, an output schema present, and full schema description coverage, the description is nearly complete for a simple two-parameter retrieval tool. It could say slightly more about failure behavior when no translated subtitle track exists, but nothing essential for correct invocation is missing.

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%, and both parameters are described there, including the supported language list. The description repeats the language list but does not add syntax, fallback, or validation semantics beyond what the schema already provides.

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: retrieve one video's translated subtitle track. It also specifies the return representation, WebVTT plus parsed cues, which makes the tool identifiable among the many TikTok sibling tools.

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?

The description implies the use case by saying it retrieves one video's translated subtitle track, but it does not explicitly state when to prefer this tool over alternatives or when not to use it. The language list is a parameter constraint rather than true usage guidance.

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?