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

douyin-ops-mcp

by kungful
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

douyin_search

Search Douyin videos or users by keyword to find content ideas, benchmark accounts, and viral post structures. Requires a logged-in Douyin session.

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": {
      "keyword": "<keyword>"
    },
    "name": "douyin_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNo排序：0 综合、1 最多点赞、2 最新发布
typeNo搜索类型，默认 video
countNo返回条数（默认 10）
offsetNo偏移，用于翻页（默认 0）
keywordYes关键词

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

The annotations only carry a title with '需登录', but the description adds the actual failure behavior: an unauthenticated call returns '请先登录'. That is genuinely useful context beyond the structured fields, though it says nothing about rate limits, result shape, or pagination behavior.

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?

It is three short sentences with zero filler: it front-loads the purpose, then the login gate, then the use-case motivation. Every sentence earns its place.

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 five-parameter search tool with no output schema, it covers purpose, auth gating, and intent well. The main remaining gap is what a result contains (fields per video or user) and how the offset and count interact for paging.

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?

The schema description coverage is 100%, so all five parameters, including the sort, type, count, and offset enums, are already documented. The description only restates the keyword and type dimensions, adding no format or usage nuance.

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 uses a specific verb and resource pair ('用关键词搜索抖音视频或用户') and names both searchable entity types, which matches the schema's type enum. It is clearly distinguishable from the download, parse, and profile sibling tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states concrete use cases ('找选题、找对标账号、找爆款结构') and a hard prerequisite (a logged-in session). It does not name alternatives or exclusions, but no sibling tool overlaps as a search entry point, so the gap is minor.

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