Skip to main content
Glama

submit_verdict

Submit a video verdict (A/B/C) to trigger server-side blocking, liking, or notification actions with automatic progress saving and duplicate prevention.

Instructions

推荐入口。提交 A拉黑/B优秀/C其他的判定,服务端执行拉黑或点赞+抖音收藏/B站通知并保存进度。失败可用相同参数继续,已成功动作不会重复执行。先 get_video_detail 获取画面和材料。

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>",
      "verdict": "<verdict>",
      "category": "<category>",
      "reason": "<reason>",
      "evidence": "<evidence>"
    },
    "name": "submit_verdict"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonYes依据用户标准的具体理由
verdictYes
categoryYes自定义分类标签;visual/work 类别需要画面证据
evidenceYes材料中的具体事实;缺失信息不能编造
platformYes平台
video_idYes视频ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden, and it does well on the hard parts: it discloses the actual side effects (blocking an author, liking, Douyin collection, Bilibili notification, progress persistence) and a non-obvious idempotency contract (already-succeeded actions are not re-executed on retry). It stops short of describing what the response reports or what permission/auth requirements apply, so it is strong but not exhaustive.

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?

Four short clauses, front-loaded with the entry-point role, then verdict semantics, then failure/idempotency behavior, then the prerequisite call. Every clause carries information an agent needs; nothing is redundant padding.

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 no output schema and no annotations, the definition still covers the critical unknowns: irreversible side effects, partial-failure recovery, and the required precursor tool. The main remaining gap is that it never says what a successful submission returns, so an agent cannot predict the response shape — a minor but real omission for a 6-parameter mutation tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 83%, giving a baseline of 3, and the description adds real meaning on top by decoding the verdict enum values (A/B/C) into concrete server behaviors — information the bare enum does not carry. It adds nothing about reason, evidence, category or platform beyond the schema's own descriptions, so it sits just above baseline rather than at the top.

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?

States a concrete verb+resource (submit an A/B/C verdict on a video) and spells out the mapping between the verdict values and server actions: A = block author, B = like + Douyin collect / Bilibili notify, C = other. It also positions itself as the recommended entry point and names get_video_detail as the preceding step, so an agent can distinguish it from the surrounding 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?

Explicitly prescribes the workflow: call get_video_detail first to obtain the visual frame and supporting material, then submit. It also gives retry guidance (reuse identical parameters after a failure). It does not name when NOT to use it or contrast with alternatives such as block_author/like_video/collect_video directly, which keeps it below a 5.

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