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

douyin-creator-mcp

by caidabai123
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

douyin_browser_sync_creator_data

Assess platform risk, then synchronize creator's video list and page visibility metrics for analysis.

Instructions

确认平台风险后同步作品列表及页面可见指标。

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_sync_creator_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNovisible
forceNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are provided, so the description must fully convey behavioral traits. It only states it syncs data after risk confirmation, lacking details on side effects, mutability, failure modes, rate limits, or what 'sync' entails (e.g., overwrite or append). This is insufficient for safe agentic invocation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single short sentence, which is concise but at the expense of omitting critical details. It front-loads the core action but lacks structure and completeness.

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

Completeness1/5

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

Given no schema descriptions, no annotations, an output schema (content unknown), and many sibling tools, the description is severely incomplete. It fails to explain the tool's role within the family, parameter semantics, or return value structure.

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 does not explain the two parameters (mode, force). The agent has no information about their purpose, allowed values, or impact on tool behavior.

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 syncs a list of works and visible metrics after risk confirmation. It identifies the action (sync) and resource (creator data). However, it does not differentiate from sibling tools like douyin_browser_sync_video_details or douyin_browser_sync_if_needed, which also perform syncing.

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 explicit guidance on when to use this tool versus alternatives. The description mentions a prerequisite (confirming platform risk) but does not specify when to use it instead of other sync tools or the expected context.

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