Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

tiktok_mobile_live_search

Read-only

Search TikTok LIVE streams by required keyword and return room anchors with host and viewer context. A keyword-less upstream request can return an empty success envelope, so the service requires a search term.

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": "tiktok_mobile_live_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNoResults to request; zero uses the app default, maximum 50.
keywordYesKeyword to search TikTok LIVE streams.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds genuinely non-obvious upstream behavior: a keyword-less request can return an empty success envelope, which explains why the term is mandatory and warns the agent about a misleading empty result. That is real behavioral value beyond the annotations.

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

Conciseness5/5

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

Two sentences, front-loaded with purpose and return shape, followed by the constraint rationale. No boilerplate or restated name/title; every sentence carries information.

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?

An output schema exists, so return-value detail is not required in the description, and the annotations carry the safety profile. The description covers purpose, the mandatory-input rationale, and a hint of the returned structure, making it complete enough for a simple two-parameter search tool.

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 both parameters are already documented in the schema, including the keyword's constraint. The description reinforces why keyword is required but adds no syntax, format, or value semantics beyond the schema. 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?

States a specific verb and resource ('Search TikTok LIVE streams by required keyword') and further specifies the return ('room anchors with host and viewer context'). The 'LIVE streams' qualifier clearly distinguishes it from the many other tiktok_mobile_* siblings (feed, hashtag, search, live_effects, live_gifts).

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?

It explains the keyword requirement ('the service requires a search term') with a rationale, which is useful. However, it gives no guidance on when to choose this tool over related siblings such as tiktok_mobile_search or tiktok_mobile_feed, nor any usage context beyond the mandatory parameter.

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

All Crawlora MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources