Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

tiktok_mobile_live_tabs

Fetches the TikTok mobile LIVE tab catalogue, returning each tab's ID, name, style, flags, and exact feed URL templates so apps can route live feeds correctly.

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).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "tiktok_mobile_live_tabs"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A3.6/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 it does disclose useful traits: the returned `data[]` shape, tab fields, the exact feed-template URL, and host behavior including the 403 from non-webcast hosts. It does not cover auth or rate limits, but for a fetch operation it provides substantial context.

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?

The description is front-loaded with the core purpose and then adds return-shape and host details. It is mostly efficient, though the internal 'round 553' reference and unusually long example URL are slightly less agent-relevant than the rest.

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?

Because there is no output schema and no annotations, the description needs to explain returned data, and it does so by naming `data[]` and its key fields. It also explains the webcast-host constraint, leaving only minor gaps such as deeper flag semantics.

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 takes zero parameters, so the baseline is 4. The description correctly does not invent parameter semantics and simply describes the resource and return shape.

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 clarifies that it returns the app's LIVE tab catalogue. This is clear enough to distinguish it from general search-tab tools, though it does not explicitly name or contrast any sibling tool.

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?

There is no explicit guidance on when to use this tool versus alternatives such as tiktok_mobile_search_tabs, tiktok_mobile_live_search, or other TikTok live-adjacent siblings. The implied use is obvious from the name, but the description adds no routing conditions or exclusions.

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