Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get TikTok live info

tiktok_live_info_get
Read-onlyIdempotent

Retrieve current room details and engagement counts for a TikTok live broadcast by supplying the room ID and numeric user ID.

Instructions

Get current room details and engagement counts for a TikTok live broadcast. Requires roomId and userId.

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": {
      "roomId": "<roomId>",
      "userId": "<userId>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "tiktok_live_info_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
roomIdYesTikTok live room id, available from the profile live lookup when the creator is broadcasting.
userIdYesTikTok numeric user id for the live owner, available from the profile live lookup.
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

A3.5/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered without the text. The description adds only that values are 'current' (a live snapshot) and that engagement counts come back alongside room details; it says nothing about rate limits, auth requirements, or error behavior when the room is offline.

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?

Two short sentences with the capability front-loaded and the prerequisite second; there is no filler. The second sentence is largely redundant with the schema's required array, which is the only thing keeping it from a top score.

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?

With no output schema, the description does signal what comes back ('room details and engagement counts'), and the parameters and safety profile are fully covered by the schema and annotations respectively. The remaining gap is that it does not say what happens when the creator is not currently broadcasting.

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 every parameter including context, llm_model and conversation_id is already documented in the schema. The sentence 'Requires `roomId` and `userId`' merely restates the required list and adds no format or sourcing detail beyond what the schema provides.

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 gives a specific verb and resource: it retrieves 'current room details and engagement counts' for a TikTok live broadcast. That is clearly distinct from the profile-level live check sibling, though the description never names that sibling or states the boundary explicitly.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: the tool applies to 'a TikTok live broadcast', so the agent can infer it is only meaningful when the creator is actively live. There is no explicit when-not guidance and no named alternative (e.g. the profile live check used to obtain the ids).

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