Skip to main content
Glama

tiktok_video_info

Extract detailed metadata including stats, audio, hashtags, and descriptions from any TikTok video URL to analyze content performance and structure.

Instructions

Get detailed metadata for a specific TikTok video (stats, audio, hashtags, description).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
video_urlYesTikTok video URL or video ID

Implementation Reference

  • The handler implementation for 'tiktok_video_info' which calls 'browser.get_video_info'.
    elif name == "tiktok_video_info":
        info = await browser.get_video_info(arguments["video_url"])
        return [TextContent(type="text", text=json.dumps(info, indent=2, ensure_ascii=False))]
  • The tool definition and input schema for 'tiktok_video_info'.
    Tool(
        name="tiktok_video_info",
        description="Get detailed metadata for a specific TikTok video (stats, audio, hashtags, description).",
        inputSchema={
            "type": "object",
            "properties": {
                "video_url": {"type": "string", "description": "TikTok video URL or video ID"},
            },
            "required": ["video_url"],
        },
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While it states this is a 'Get' operation (implying read-only), it doesn't mention any behavioral traits such as rate limits, authentication requirements, error conditions, or what happens with invalid URLs. For a tool with no annotation coverage, this leaves significant gaps in understanding its operational characteristics.

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?

The description is extremely concise and front-loaded in a single sentence that efficiently communicates the core functionality. Every word earns its place with no wasted verbiage or unnecessary elaboration.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of video metadata retrieval (which could involve various data points and potential failures) and the absence of both annotations and an output schema, the description is insufficiently complete. It doesn't explain what specific metadata is returned, how errors are handled, or any prerequisites for successful operation, leaving the agent with inadequate context for reliable use.

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%, with the single parameter 'video_url' clearly documented in the schema as accepting 'TikTok video URL or video ID'. The description adds no additional parameter semantics beyond what's already in the schema, so it meets the baseline for adequate coverage without adding value.

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 clearly states the tool's purpose with a specific verb ('Get') and resource ('detailed metadata for a specific TikTok video'), and it lists the types of metadata included (stats, audio, hashtags, description). However, it doesn't explicitly differentiate from sibling tools like 'tiktok_user_videos' or 'tiktok_search' which might also provide video metadata in different contexts.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. With siblings like 'tiktok_search', 'tiktok_user_videos', and 'tiktok_feed' that might overlap in functionality, there's no indication of when this specific metadata retrieval tool is preferred or what distinguishes it from other video-related tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/follox42/tiktok-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server