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

douyin-ops-mcp

by kungful
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

douyin_batch_download

Downloads multiple Douyin videos from a creator's profile, keyword search results, or the trending feed. Supports limits, cursor pagination, auto-deduplication, and skips already-downloaded works for research and material libraries.

Instructions

批量下载：某个博主主页的全部/部分作品、关键词搜索命中的作品、或当前热点视频流。带 limit 与游标控制，自动去重、自动跳过已下载。适合做选题拆解、竞品分析、素材库。注意有频率风控，一次别拉太多（建议 limit ≤ 30）。

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": {
      "source": "<source>",
      "limit": "<limit>"
    },
    "name": "douyin_batch_download"
  }
}

Input Schema

NameRequiredDescriptionDefault
dirNo保存目录
limitYes最多下载多少个作品（默认 10，建议 ≤30）
musicNo是否下载背景音乐（默认 false）
cursorNo分页游标（上一页返回的 cursor，默认 0）
sourceYesuser=博主主页；search=关键词搜索（需登录）；hotspot=热点视频流（免登录）
targetNouser：主页链接或 sec_uid；search：关键词；hotspot：留空

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only carry a title, so the description carries the full burden and largely meets it: it discloses automatic deduplication, automatic skipping of already-downloaded items, cursor-based pagination, and a rate-limit risk with a suggested cap. What it omits is failure behavior — whether a mid-batch rate-limit error aborts or partially completes the download.

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?

A single dense sentence with the resource scopes front-loaded, followed by the control and safety caveats. No filler, though the run-on enumeration of three sources plus use cases plus limit advice in one block is slightly harder to scan than separate clauses.

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?

With six parameters, no output schema, and only a title annotation, the description supplies the missing behavioral layer — sources, dedup, skipping, pagination, and rate limits. It stops short of stating what a batch returns (count of new vs skipped files) or how to resume from an error, which matters for a batch tool.

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%, so the schema already explains source, target, cursor, dir, music, and limit. The description only reinforces limit and cursor with the ≤30 advice, which is useful but does not add meaning beyond the structured fields.

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 enumerates the three resource scopes it covers: a creator's homepage works, keyword-search hits, and the hotspot feed. An agent can tell what it fetches, though it never names the sibling single-item tool (douyin_download) or douyin_search to draw the line explicitly.

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 use-case framing (选题拆解、竞品分析、素材库) and a concrete throttle guideline (limit ≤ 30), which is genuinely actionable. However it does not say when to prefer this over douyin_download or douyin_search, nor what to do when the batch is empty, so the routing decision is left implied.

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