Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

tiktok_post

Fetch a TikTok video's details by video ID, returning its description, author profile and stats, plus share metadata.

Instructions

Retrieve TikTok video details. Returns TikTok's detail record for one video by video id. itemInfo.itemStruct holds the video's description, the author's profile and the author's statistics (such as followers, following and hearts) along with the rest of TikTok's video object; shareMeta holds the share title and description.

Input Schema

NameRequiredDescriptionDefault
idYesTikTok video id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It does add real value by naming the returned structure ('itemInfo.itemStruct' with description, author profile and stats; 'shareMeta' with share title/description), but it says nothing about read-only nature, permissions, or failure modes for a missing/invalid id.

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?

Front-loaded with the core action, then the return-shape detail. The second and third sentences are dense with field paths, but given the absence of an output schema this detail earns its place rather than being filler.

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?

For a one-parameter lookup with no output schema, the description compensates by describing the shape of the returned record, which is exactly what an agent otherwise could not know. The remaining gap is the missing sibling differentiation and any note on invalid-id behavior.

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% and there is a single parameter documented as 'TikTok video id'. The description's phrase 'by video id' merely restates the schema and adds no format or example detail beyond it, so the baseline of 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 ('Retrieve TikTok video details ... by video id'), which is clearer than the bare name 'tiktok_post'. It does not, however, distinguish itself from the sibling 'tiktok_posts', leaving an agent to guess whether the singular tool is the detail fetch and the plural the list.

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 only implied: the description says it works 'by video id', which tells the agent what input is needed but not when to prefer this over tiktok_posts, tiktok_search, or tiktok_profile. No exclusions or prerequisites are stated.

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