Skip to main content
Glama

block_author

Block authors on Bilibili or Douyin with a required reason, applying local blacklists immediately and platform blocks according to dry-run settings.

Instructions

拉黑作者(判 A 用)。本地黑名单立刻生效,平台拉黑要看 curate.dryRun。reason 必填:写清命中标准哪一条。

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>",
      "author_id": "<author_id>",
      "reason": "<reason>"
    },
    "name": "block_author"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonYes拉黑理由,必填:命中标准的哪一条
sec_uidNo抖音必填,取 list_feed 返回的 author.secUid
platformYes平台
author_idYesB站 mid / 抖音数字 uid
author_nameNo作者名(审计用)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full load and does disclose real behavior: the local blacklist applies immediately, while platform-level blocking depends on curate.dryRun. That is exactly the kind of asymmetry an agent needs before calling a mutation tool. It omits reversibility, permission requirements, and error behavior, and the referenced curate.dryRun is not defined here.

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?

Three short, front-loaded clauses with no filler: action, behavioral caveat, then the required-field rule. The term "curate.dryRun" is unexplained and slightly cryptic, costing a point, but nothing is wasted.

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 mutation tool with no annotations and no output schema, the description covers the crucial points: when to use it, the immediate-vs-dry-run distinction, and the mandatory justification. It leaves gaps on error handling and how to reverse the block, but the agent has enough to call it correctly.

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 coverage is 100%, so platform, author_id, sec_uid, author_name, and reason are all already documented in the schema. The description's reminder that reason must state which criterion was hit largely restates the schema text for that field. Baseline 3 is appropriate because the schema does the heavy lifting.

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 opens with a specific verb+resource ("拉黑作者") and adds a qualifying scope ("判 A 用"), so the agent knows exactly what operation this performs and in which verdict context. It does not explicitly name unblock_author as the inverse, but the purpose itself is unambiguous.

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?

The parenthetical "判 A 用" gives a concrete condition that selects this tool (only invoked when the criteria verdict is A), and the note about curate.dryRun clarifies how platform-level blocking behaves. It stops short of naming alternatives such as unblock_author or get_criteria, so the guidance is clear but not exhaustive.

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