Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

tiktok_mobile_live_room

Fetch a TikTok LIVE room by numeric room_id to get status, concurrent viewers, owner details, stream URLs, and cover image.

Instructions

LIVE room detail: status, viewers, owner, stream URLs, cover. Returns one LIVE room's detail, keyed by room_id — the numeric id that /api/v1/tiktok/mobile/live/search returns under data[].lives.author.room_id. The upstream is /webcast/room/info/ on the webcast edge host (no origin header), captured from the running 47.4.3 app's LIVE surface and reproduced against the live gateway. The response projects the fields callers key on — title, status (2 = live), user_count (concurrent viewers), create_time, owner (user id, nickname, avatar), stats (cumulative enter_count/total_user, watch_user_count, like_count, comment_count, share_count, follow_count, replay_viewers), stream (playable flv_pull_url per resolution plus default_resolution/candidate_resolution and the HLS/RTMP URLs) and cover — and keeps the upstream room object unmodified in data (it has ~500 keys, so a partial struct would drop fields). Measured 2026-10-22: one room returned 193-198 KB with 1,595-1,600 concurrent viewers, 27,916 cumulative viewers, 27,096 enters and FLV URLs for FULL_HD1/HD1/SD1/SD2. anchor_id is deliberately NOT forwarded: it was measured to suppress the audience-only stats.total_user (27,916 -> 0 on the same room). A missing, non-numeric or unknown room id answers the webcast envelope's status 10011 and is surfaced as a 400; a finished room (status 30003) is a 400 too.

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": {
      "room_id": "<room_id>"
    },
    "name": "tiktok_mobile_live_room"
  }
}

Input Schema

NameRequiredDescriptionDefault
room_idYesNumeric LIVE room id from /api/v1/tiktok/mobile/live/search (data[].lives.author.room_id)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A4.4/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so thoroughly: it lists returned fields, explains the unmodified `data` object with ~500 keys, documents the `anchor_id` omission and its measured effect, and describes 400 error cases for invalid or finished rooms. This gives the agent unusually rich behavioral context for a read-only detail endpoint.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

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

The description is front-loaded and structured, but it is far too long for a one-parameter detail tool. Measured byte sizes, exact viewer counts, capture dates, and app-version provenance do not help an agent decide when or how to call the tool, so several sentences do not earn their place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema and no annotations, so the description must explain return shape and error behavior. It does that comprehensively, including projected fields, the preserved upstream object, stream URL formats, and 400 responses for invalid or finished rooms. 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.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already defines `room_id` and its source. The description adds useful validation semantics by stating that missing, non-numeric, or unknown room ids are surfaced as 400, and it clarifies that `anchor_id` is deliberately not forwarded. This is meaningful beyond the schema, though only one parameter is involved.

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 first sentence names a specific resource and operation: 'LIVE room detail' and 'Returns one LIVE room's detail.' It also anchors the tool to `room_id` obtained from `/api/v1/tiktok/mobile/live/search`, which clearly separates it from the search sibling. The purpose is immediately clear.

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?

The description explains where the required `room_id` comes from, implying the correct workflow: search first, then fetch room detail. It also states that missing, non-numeric, unknown, or finished room ids return a 400, which helps avoid misuse. It does not explicitly compare against the `tiktok_mobile_live_room_by_user` sibling, so it stops short of a 5.

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