Skip to main content
Glama

collect_video

Saves a Bilibili or Douyin video to favorites with an optional reason while honoring dry-run mode and daily collection quotas.

Instructions

收藏(抖音判 B 时配合点赞;B站 可选)。受 actions.dryRun 和 collectPerDay 约束。

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": {
      "platform": "<platform>",
      "video_id": "<video_id>"
    },
    "name": "collect_video"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNo为什么收藏
platformYes平台
video_idYesbvid 或 aweme_id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the disclosure burden and does add real behavior: the call is gated by actions.dryRun and by a collectPerDay quota, implying suppressed execution in dry-run and a daily cap. It still says nothing about failure modes, idempotency, or what a successful collect returns, so it is helpful but incomplete for a mutation 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 short clauses, front-loaded with the action and conditional rule, with the constraint noted second. Nothing is wasted, though the terse parenthetical phrasing requires the reader to parse the platform rule carefully.

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?

For a 3-parameter mutation tool with no annotations and no output schema, the description covers the operational constraints (dry-run, daily cap) but omits authentication needs, error behavior, and any sense of the response. Adequate but with clear gaps given the tool's complexity.

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 all three parameters (reason, platform, video_id) are already documented, which sets the baseline at 3. The description adds a little by implying which platform warrants collecting, but gives no syntax or format detail the schema lacks.

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 the action (收藏/collect) and ties it to a platform-specific rule, so the agent knows it records a video as a favorite. It does not explicitly distinguish itself from the sibling like_video beyond noting the two can be paired, so it stops short of a 5.

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 gives concrete when-to-use guidance: on Douyin, collect when the verdict is B and pair it with a like; on Bilibili, collecting is optional. That is clear contextual routing, though it never states when not to use the tool or names an alternative to prefer instead.

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