redfox-mcp

Official

Overview Schema Source Related Servers Discussions Admin

douyin_get_work

Retrieve detailed Douyin video data including engagement metrics, author info, and content details by providing a work ID or video URL. Uses a curated high-quality data source.

Instructions

获取抖音作品详情（优质库）。work_id 与 work_url（作品链接）至少传一个，返回互动数据、作者信息等。

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

Input Schema

Name	Required	Description	Default
`work_id`	No
`work_url`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 18, 2026

TDQS

A3.5/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 carry the full behavioral disclosure. It only states what is returned (interaction data, author info, etc.) without mentioning any side effects, authentication needs, rate limits, or error behavior. For a data retrieval tool, more transparency is expected.

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?

Two short sentences, no filler. The purpose and parameter condition are front-loaded. Every word earns its place.

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

Completeness3/5

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

The tool has an output schema (not shown) which can define the return structure, so the description's high-level summary ('互动数据、作者信息等') is acceptable. However, it lacks coverage of error conditions, authentication context, or detailed scope explanation of '优质库'. Adequate but has gaps.

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

Parameters4/5

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

Schema description coverage is 0%, but the description explicitly links both parameters to their real-world meaning: 'work_id' and 'work_url' (作品链接). It also states the constraint that at least one must be provided. This adds significant semantic value beyond the raw schema, though examples or formats would be beneficial.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb '获取' (get) and the resource '抖音作品详情' (Douyin work details). It includes the scope '优质库' (premium library), which distinguishes it from other Douyin tools like 'douyin_get_user' or 'douyin_search_articles'. The requirement to provide either work_id or work_url further differentiates it as a detail retrieval for a single work.

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 gives parameter usage guidance (at least one of work_id/work_url required) but no explicit advice on when to use this tool versus siblings like 'douyin_get_user_works' or 'douyin_search_articles'. No exclusions or alternatives are mentioned.

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

Deploy Server