Skip to main content
Glama
Sign In
douyin-creator-mcp

douyin-creator-mcp

by caidabai123
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

douyin_browser_export_data

Export Douyin creator data snapshots and derived metrics in JSON or CSV to enable offline analysis and comparison.

Instructions

导出本地快照和派生指标；V1 支持 JSON 与 CSV。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "douyin_browser_export_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNojson
periodNoall
output_pathNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations exist, so the description must disclose behavior. It does not mention whether the export is read-only, destructive, or requires specific authentication. The term 'local' suggests data is exported from a local cache, but this is unclear.

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?

The description is very short—two sentences—with no redundant words. However, it omits critical details, sacrificing substance for brevity.

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 moderate complexity (3 parameters, output schema exists), the description is insufficient. It does not explain return values, parameter constraints, or how to handle different periods. Agents lack enough information to use the tool correctly.

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

Parameters1/5

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

Schema description coverage is 0%, and the description only hint at the format parameter by mentioning JSON and CSV. The 'period' and 'output_path' parameters are entirely unexplained, leaving agents to guess their meaning.

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 exports local snapshots and derived metrics, and mentions supported formats (JSON and CSV). It distinguishes itself from sibling tools which focus on login, sync, listing, and analysis.

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 other tools, no prerequisites, and no context about typical usage scenarios. Agents must infer usage purely from the name.

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