Skip to main content
Glama

tiktok_download

Download TikTok videos directly from URLs, removing watermarks when available to save content locally.

Instructions

Download a TikTok video (without watermark when possible).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
video_urlYesTikTok video URL
output_pathNoOutput file path (optional, auto-generated if empty)

Implementation Reference

  • The handler logic for "tiktok_download" in server.py, which processes the input arguments, generates an output path, and calls the browser's download method.
    elif name == "tiktok_download":
        video_url = arguments["video_url"]
        output_path = arguments.get("output_path", "")
        if not output_path:
            import re
            m = re.search(r"/video/(\d+)", video_url)
            vid_id = m.group(1) if m else str(int(datetime.now().timestamp()))
            output_path = os.path.join(DOWNLOAD_DIR, f"{vid_id}.mp4")
    
        result = await browser.download_video(video_url, output_path)
        return [TextContent(type="text", text=json.dumps(result, indent=2, ensure_ascii=False))]
  • The tool registration and schema definition for "tiktok_download".
    Tool(
        name="tiktok_download",
        description="Download a TikTok video (without watermark when possible).",
        inputSchema={
            "type": "object",
            "properties": {
                "video_url": {"type": "string", "description": "TikTok video URL"},
                "output_path": {"type": "string", "description": "Output file path (optional, auto-generated if empty)"},
            },
            "required": ["video_url"],
        },
    ),
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'without watermark when possible,' which hints at a best-effort behavior, but doesn't cover critical aspects like file format, download location defaults, error handling, rate limits, or authentication needs. For a download tool that likely involves external network calls, this is insufficient.

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 a single, efficient sentence with zero waste. It's front-loaded with the core action and includes a useful qualifier. Every word earns its place, making it highly concise and well-structured.

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 a download operation (network-dependent, file I/O) with no annotations and no output schema, the description is incomplete. It lacks details on return values (e.g., success/failure indicators, file path), error conditions, or behavioral constraints. The 'without watermark when possible' hint is helpful but doesn't compensate for the overall gaps.

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 the schema already documents both parameters (video_url and output_path). The description doesn't add any parameter-specific details beyond what's in the schema, such as URL format examples or auto-generation rules for output_path. Baseline 3 is appropriate when the schema does the heavy lifting.

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 verb ('Download') and resource ('a TikTok video'), with the additional qualifier 'without watermark when possible' providing useful context. It distinguishes from siblings like tiktok_video_info (which likely provides metadata) and tiktok_publish (which uploads content), though it doesn't explicitly name these alternatives.

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?

No guidance is provided on when to use this tool versus alternatives. For example, it doesn't clarify whether this should be used instead of tiktok_video_info for downloading versus just getting metadata, or whether there are prerequisites like having a valid URL format. The description only states what it does, not when to choose it.

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