Skip to main content
Glama

like_video

Like Bilibili or Douyin videos as curation decisions while honoring dry-run settings and daily like quotas; record each reason for audit.

Instructions

点赞(判 B 用)。受 actions.dryRun 和 likePerDay 约束。

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": "like_video"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNo为什么值得点赞(写进审计)
platformYes平台
video_idYesbvid 或 aweme_id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

C2.7/5.0
Behavior3/5

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

With no annotations at all, the description carries the full burden. It does disclose two real behavioral constraints, namely that the action is subject to actions.dryRun and to a likePerDay quota, which is genuine context beyond the schema. However, it does not say what happens when the quota is hit, what dry-run actually does (simulate vs. no-op), or whether a like is reversible, leaving important mutation behavior implicit.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short and front-loads the action, but brevity here shades into under-specification: the parenthetical and the two constraint names are compressed into unexplained shorthand. Every sentence could earn its place if the jargon were expanded, but as written the density obscures meaning rather than helping.

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

Completeness2/5

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

This is a write operation with no annotations and no output schema, so the description should explain side effects, auth requirements, and quota-failure behavior. It names the dryRun and likePerDay constraints but never explains their consequences or the return/audit behavior, so an agent cannot predict the outcome of a call from the definition.

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 all three parameters are individually documented, including the enum for platform and the id format for video_id, so the schema already does the heavy lifting. The description adds no meaning about reason or the identifiers, which is acceptable at this coverage level.

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

Purpose3/5

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

The verb '点赞' (like) plus the object (a video identified by platform/video_id) gives a recognizable action, but the parenthetical '判 B 用' is unexplained jargon that leaves the purpose only partially clear. It does not distinguish this from siblings such as collect_video or submit_verdict, so an agent cannot tell from the text why it would like rather than collect.

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 only usage cue is the cryptic '判 B 用' (for judging B), which hints at a workflow but never states the condition for using this tool, when not to use it, or which sibling handles the alternative. No prerequisites, no exclusions, no named alternative.

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