Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Check TikTok creator livestream status

tiktok_profile_live_check
Read-onlyIdempotent

Check whether a TikTok creator is currently broadcasting a livestream by handle. Returns public live-status data so you can confirm a broadcast is active before engaging.

Instructions

Check whether the TikTok creator specified by handle is currently broadcasting a livestream. Returns public live-status data. Requires handle.

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": {
      "handle": "<handle>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "tiktok_profile_live_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
handleYesRequired. TikTok handle to look up, with or without a leading @.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare this read-only, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds one genuine piece of context: it returns public live-status data, implying no private/authenticated fields. It says nothing about what an offline creator yields (false vs. error), freshness/latency of the status, or rate limits.

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?

Three short sentences with the core purpose front-loaded. The trailing 'Requires `handle`' is largely redundant with the schema's required list and the handle field's 'Required.' description, but it costs almost nothing.

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

Completeness3/5

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

For a simple single-lookup read tool with full annotation coverage, the definition is close to sufficient. However, with no output schema, the description should say more about the return shape (boolean flag vs. stream metadata) than the vague 'public live-status data', and it omits any sibling routing.

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 description coverage is 100%, so all four parameters (handle, context, llm_model, conversation_id) are already documented in the schema, including the @-optional handle format. The description only restates that handle is required, adding no meaning beyond structured data; baseline 3 applies.

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?

States a specific verb and resource: check whether the creator identified by handle is currently broadcasting a livestream. That is distinguishable from the profile-detail siblings (followers, videos, region). It does not, however, differentiate itself from the close sibling `tiktok_live_info_get`, leaving the agent to guess which live-related tool returns what.

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?

No guidance on when to prefer this over `tiktok_live_info_get` or the broader profile tools, and no stated preconditions beyond the parameter requirement. Usage is only implied by the name and one-line purpose, so an agent has no routing rule when multiple live/profile tools are available.

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