Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

tiktok_mobile_live_gifts

Retrieve every TikTok LIVE gift with details, configs, and resource maps in a single call for gift tracking, overlays, or analytics.

Instructions

Retrieve TikTok LIVE gifts. Returns the complete LIVE gift catalogue in one call: data.gifts (771 gift objects with diamond_count, describe, duration, gift_resources, gift_skins, batch_gift_info and combo) plus the gift config and resource maps (gift_configs, gifts_info, doodle_templates, gift_name_group_map, gift_resource_group_map). There are no request parameters and no paging: the response is a single complete catalogue.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.13

TDQS

A4.2/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden, and it does well: it explicitly says there are no request parameters and no paging and that the entire catalogue arrives in a single response. It stops short of stating freshness or whether the catalogue is cached, which would have completed the behavioral picture.

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 sentences, front-loaded with the core action and then the return shape; the enumeration of fields is information-dense rather than padded. Slightly heavy on payload detail, but each clause earns its place by telling the agent what it will get back.

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?

For a zero-parameter catalogue tool with no output schema, the description compensates by naming the top-level response keys and the gift object fields, so an agent knows exactly what a call yields. Nothing needed to invoke it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the baseline is 4. The description correctly reinforces this by stating there are no request parameters, which prevents an agent from inventing one.

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 (Retrieve) and resource (TikTok LIVE gifts) and goes further by enumerating the exact return payload, so an agent can distinguish it from tiktok_mobile_live_search and tiktok_mobile_live_effects without opening any schema.

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?

The description clarifies the calling model (no parameters, no paging, one complete call), which effectively implies usage. But it never states when to reach for this tool versus the closely named siblings tiktok_mobile_live_effects or tiktok_mobile_live_search, nor any exclusions.

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