Skip to main content
Glama

unblock_author

Removes an author from the local blacklist and attempts to lift the platform block, restoring access after a mistaken block decision.

Instructions

取消拉黑(误判回滚用):移出本地黑名单并尽量解除平台拉黑。

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>"
    },
    "name": "unblock_author"
  }
}

Input Schema

NameRequiredDescriptionDefault
sec_uidNo抖音 sec_user_id
platformYes平台
author_idYes作者 id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose key behavior: it targets both the local blacklist and the platform, and 尽量解 ("attempt to lift") signals best-effort, possibly partial success. It says nothing about what happens when the author isn't blocked, whether re-blocking is possible, or how partial failure is reported.

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?

One compact sentence pairs the action with a parenthetical usage note, front-loading the tool's identity. There is no redundant or filler wording.

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?

The parameters are fully covered by the schema, but for a mutation tool with no annotations and no output schema, the description never explains what a caller gets back when the local removal succeeds but the platform unblock fails. That partial-failure case is the crux of this tool and remains unspecified.

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 platform, author_id, and sec_uid are already documented in the schema. The description adds no per-parameter guidance, such as whether sec_uid is needed for douyin, so the baseline of 3 applies.

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 resource (取消拉黑/author) and spells out the two concrete effects: removing the local blacklist entry and attempting to lift the platform block. That reveals more than the name alone, though it doesn't explicitly name block_author as the inverse operation.

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 误判回滚用 ("for rolling back misjudgments") gives a clear condition for when this tool applies, implicitly distinguishing it from ordinary moderation. It stops short of stating prerequisites (for example, checking with get_blacklist first) or explicit when-not-to-use cases.

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