Skip to main content
Glama

TokConnect: TikTok Research

Search LIVE now

live_search
Read-only

Finds TikTok LIVE broadcasts on now by keyword, with viewers and whether the room sells Shop products. Pass a room id to live. Not a sales ranking (use live_top_selling). Example: {"keyword":"skincare"}.

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": {
      "keyword": "<keyword>"
    },
    "name": "live_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoResults per page. Max 30. Values above a method's maximum are lowered and reported in notes.
cursorNoPaging: pass the next value from the previous response unchanged. Omit on the first page.
detailNocompact (default) returns the useful fields; full adds the full raw record (large).compact
regionNoMarket as an ISO country code, default US. Shop Analytics methods: sales data for that market, amounts in its currency. Live methods that take it (search, video detail, creator posts, Shop pages): TikTok as seen in that market where TikTok serves it. Core: US, GB, DE, FR, ES, JP, TH, VN, ID, MY, PH, BR, MX. Extended: PL, IT, NL, IE. Other countries are refused. See shop_regions.
keywordYesSearch phrase, e.g. 'lip oil'.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / detail / description
      Previous value: -"compact (default) returns the useful fields; full adds the raw upstream payload (large)."New value: +"compact (default) returns the useful fields; full adds the full raw record (large)."
  2. Changed1 schema field changed
    • addedInput schema / properties / region
      Added value: +{
      +  "description": "Market as an ISO country code, default US. Shop Analytics methods: sales data for that market, amounts in its currency. Live methods that take it (search, video detail, creator posts, Shop pages): TikTok as seen in that market where TikTok serves it. Core: US, GB, DE, FR, ES, JP, TH, VN, ID, MY, PH, BR, MX. Extended: PL, IT, NL, IE. Other countries are refused. See shop_regions.",
      +  "maxLength": 2048,
      +  "type": "string"
      +}
  3. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already establish that this is a read-only, open-world, non-idempotent operation. The description adds useful behavioral context by saying results are LIVE broadcasts on now and by naming two returned signals (viewers and Shop product status), though it does not discuss pagination or rate limits directly.

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 short and front-loaded, stating the main search behavior first, then the alternative, then an example. The sentence about passing a room id to live is useful for follow-up but slightly indirect in context.

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 an output schema present, the description need not explain return values in detail, and it still summarizes the important signals. It is complete enough for correct invocation, with only minor gaps around pagination or region behavior that are covered by the schema.

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 parameters like cursor, detail, region, and limit are already well documented. The description adds a concrete keyword example but does not add much beyond the schema for the remaining parameters; a baseline 3 is appropriate.

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 uses a specific verb and resource: it finds TikTok LIVE broadcasts that are on now by keyword. It also states key returned attributes (viewers, whether the room sells Shop products) and explicitly distinguishes the tool from live_top_selling.

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 clearly tells the agent to use this for keyword-based LIVE discovery and explicitly names the alternative for sales rankings: live_top_selling. The example reinforces the expected call shape, and the follow-up mention of live helps sequence tool use.

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.

Resources