Skip to main content
Glama

douyin_my_videos

Retrieve your Douyin creator work list with play, like, comment, share, and status metrics to review performance and identify posts for promotion.

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

Input Schema

NameRequiredDescriptionDefault
limitNo最多多少条(默认 20)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

The annotations carry only a title, so the description bears the safety burden, and it does disclose the data source (the creator center works management page), implying a logged-in creator session is required. It does not mention pagination behavior, whether all works are fetched or only a first page, or what happens when the session is unauthenticated — meaningful gaps for a scraping-style read tool.

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?

Two sentences, front-loaded with the action and source before the analytical purpose. The closing clause about retrospectives and 投流 is slightly promotional but does convey legitimate use context rather than pure 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 read tool with no output schema, the description usefully enumerates the returned metrics, which is the main thing an agent could not infer from structured fields. What remains thin is authentication and paging behavior, but the core is covered.

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 the single parameter already documents its own default of 20, so the description adds nothing about the limit or ordering. The baseline of 3 applies: the schema does the work and the description does not compensate or extend it.

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 names a specific verb-and-resource pair ("从创作者中心作品管理页读出我的作品列表") and enumerates the fields returned (播放、点赞、评论、分享、状态), so the agent knows exactly what data comes back. It is distinct from the per-video and account-level siblings in substance, though it never names those siblings to make the distinction explicit.

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?

It gives an implied usage context ("做复盘/找哪条该投流") that tells the agent this is for retrospective analysis of one's own catalog rather than fetching public or competitor data. However, it never states when NOT to use it or which sibling to prefer, e.g. douyin_video_stats for a single video or douyin_account_overview for aggregate account numbers.

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