Skip to main content
Glama

TikTok Live

social_tiktok_user_live
Read-only

Checks a TikTok user's live status and retrieves available live room details. First checks the account with the same profile lookup used by /v1/tiktok/profile; this does not add a second API credit charge. Active streams return HTTP 200 with is_live: true; an existing account that is offline or has no current stream returns HTTP 200 with is_live: false. Both successful states cost 1 credit, including offline/no-stream accounts. Unavailable accounts: HTTP 404 when TikTok confirms the account is not found or unavailable. Audience controls: HTTP 403 when TikTok confirms the creator enabled them, with TikTok's login warning. Retrieval failures: HTTP 500 when the live check fails. Errors cost 0 credits (credits_charged: 0); never infer offline from an error. A failed check is not evidence that the account is offline, and having no current stream is not an account-not-found error. Use the top-level is_live boolean instead of checking TikTok's numeric status values yourself. Available details include liveRoomUserInfo (nickname, avatar, followerCount, roomId) and liveRoom (title, startTime, status, liveRoomStats with enterCount and userCount, plus streamData with playback URLs in multiple qualities). When no room exists, liveRoom is omitted rather than filled with invented room data. Ended-room details remain when TikTok supplies them. A real viewer count of zero is not treated as a restriction. Completed lookups cost at least 10 Nexscope credits. Actual cost depends on the operation and requested options. Repeated requests may purchase data again. TikTok Live API View Pricing Checks TikTok live status and room details. 200 is_live:true/false costs 1 credit, including offline/no-stream accounts. Unavailable accounts: 404; audience controls: 403; retrieval failures: 500. Errors cost 0 credits; never infer offline. 1 credit per request Checks a TikTok user's live status and retrieves available live room details. First checks the account with the same profile lookup used by /v1/tiktok/profile; this does not add a second API credit charge. Active streams return HTTP 200 with is_live: true; an existing account that is offline or has no current stream returns HTTP 200 with is_live: false. Both successful states cost 1 credit, including offline/no-stream accounts. Unavailable accounts: HTTP 404 when TikTok confirms the account is not found or unavailable. Audience controls: HTTP 403 when TikTok confirms the creator enabled them, with TikTok's login warning. Retrieval failures: HTTP 500 when the live check fails. Errors cost 0 credits (credits_charged: 0); never infer offline from an error. A failed check is not evidence that the account is offline, and having no current stream is not an account-not-found error. Use the top-level is_live boolean instead of checking TikTok's numeric status values yourself. Available details include liveRoomUserInfo (nickname, avatar, followerCount, roomId) and liveRoom (title, startTime, status, liveRoomStats with enterCount and userCount, plus streamData with playback URLs in multiple qualities). When no room exists, liveRoom is omitted rather than filled with invented room data. Ended-room details remain when TikTok supplies them. A real viewer count of zero is not treated as a restriction.

Input Schema

NameRequiredDescriptionDefault
handleYesTikTok handle

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the simple read-only annotations, the description provides massive behavioral context, including the specific pricing model (1 credit vs. 0 credits), the definition of 'failed check' behavior, and the technical constraint that `liveRoom` is omitted rather than filled with invented data.

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?

While highly informative, the description is extremely verbose and repetitive. It details the same status check results multiple times across different paragraphs and sections. This length significantly detract from conciseness, even if every sentence contains value.

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?

The definition is contextually complete because it leaves virtually no ambiguity. It accounts for every possible state (active, offline, unavailable, restricted, errored) and the resulting technical output structure. The sheer volume of detail ensures an AI agent can interpret the results perfectly.

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?

Since the schema coverage is 100%, the description does not need to add semantic meaning to the input parameter 'handle'. It primarily uses the parameter context to explain API efficiency (using the same profile lookup).

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 clearly states its function: 'Checks a TikTok user's live status and retrieves available live room details.' Given the large number of TikTok sibling tools, this specific focus is highly effective.

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

Usage Guidelines5/5

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

It provides explicit logic for using the tool, advising the agent to 'Use the top-level `is_live` boolean instead of checking TikTok's numeric status values yourself.' It meticulously defines which HTTP status codes (404, 403, 200) correspond to which real-world states (offline, audience controls, etc.).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.