Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

tiktok_mobile_live_tabs

Fetch a TikTok LIVE tab catalogue with each tab’s ID, name, style, enable/event flags, and exact feed URL templates for client requests.

Instructions

Fetch the LIVE tab catalogue. Returns the app's LIVE tab catalogue: data[] holds one entry per tab with the tab's id, name, style, enable/event flags and the exact url/inter_url feed template the client calls for that tab. The measured tab 1 ("live") points at /webcast/feed/?content_type=0&style=2&channel_id=21&sub_channel_id=0&tab_id=1&type=live&sub_type=live&req_type=0&cate_id=0 on webcast.tiktokv.com. This closes the route round 553 could not find a host for; it is served by the webcast edge hosts (non-webcast hosts answer 403) and is one of the few LIVE routes that answers device-free: measured with the pure-Go placeholder signer as well as the real device signer, so it does not need the device-backed signing service.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A3.5/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 behavioral burden and does well: it discloses the return shape, the exact webcast host behavior (non-webcast hosts answer 403), and that the route works device-free with both placeholder and real device signers. It does not cover auth requirements, rate limits, or error behavior, keeping 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.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded and organized, leading with the purpose and return shape. However, it is verbose for a zero-parameter fetch tool, including an exact long URL and a reference to 'round 553' that are unlikely to help an agent invoke the tool correctly.

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?

There is no output schema or annotations, but the description compensates by explaining the `data[]` structure and key fields, plus host and signing constraints. It is reasonably complete for a simple read-only catalogue fetch, though error handling and pagination behavior are not addressed.

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?

The tool has zero parameters and 100% schema description coverage, so the baseline is 4. The description adds no parameter meaning because there are no parameters to explain.

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?

The description states a specific verb and resource: 'Fetch the LIVE tab catalogue' and explains that `data[]` contains one entry per tab with fields such as `id`, `name`, `style`, and feed URLs. It is clear what the tool returns, but it does not explicitly differentiate itself from nearby siblings like `tiktok_mobile_live_search`, `tiktok_mobile_search_tabs`, or `tiktok_mobile_live_room`.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description does not state when to use this tool versus alternatives, nor does it name any sibling tools or exclusion conditions. The reader can infer that it is for retrieving the LIVE tab catalogue, but there is no explicit usage guidance.

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