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

douyin-ops-mcp

by kungful
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

douyin_user_profile

Fetch a Douyin creator's public profile—followers, post count, bio, verification—plus recent posts to begin competitor or benchmark account analysis.

Instructions

读一个抖音博主的公开资料（粉丝、作品数、简介、认证）以及最近的作品列表。做竞品/对标账号分析的第一步。

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "target": "<target>"
    },
    "name": "douyin_user_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
postsNo顺便拉多少条作品（0 = 只拉资料，默认 10）
targetYes主页链接或 sec_uid

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

The only annotation is a title, so the description carries most of the weight. It does disclose that the data is public (公开) and read-only in nature, and it lists what comes back, which is useful context. It does not mention whether login is required, what happens with an invalid target, or rate limits.

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 waste, and the core capability is front-loaded ahead of the use-case hint. Every sentence adds information.

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?

This is a simple two-parameter read tool with no output schema, and the description covers what is fetched and the fields involved, which is enough to invoke it correctly. Minor gaps remain around auth and error behavior for a malformed target.

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 schema already explains that `posts` defaults to 10 and that 0 returns profile only, and that `target` accepts a homepage URL or sec_uid. The description adds only that the tool returns 最近的作品列表, which mirrors the `posts` parameter without adding syntax or constraints. This fits the baseline-3 case.

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 pairs a specific verb (读) with a specific resource (抖音博主的公开资料) and enumerates the exact fields returned: 粉丝、作品数、简介、认证, plus 最近的作品列表. This lets an agent separate it from siblings such as douyin_video_stats or douyin_account_overview, though those tools are never named.

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 one usage context, 「做竞品/对标账号分析的第一步」, so an agent knows when to reach for it. It says nothing about when not to use it and does not explicitly route to alternatives (e.g. douyin_search for finding a creator, douyin_video_stats for per-video numbers), leaving the choice to inference.

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