Skip to main content
Glama

get_blacklist

Retrieve the local blacklist and optionally filter entries by platform (Bilibili or Douyin) to check whether content or accounts are blocked.

Instructions

查本地黑名单(可按平台过滤)。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_blacklist"
  }
}

Input Schema

NameRequiredDescriptionDefault
platformNo平台

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

C2.9/5.0
Behavior2/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 of disclosing behavior. It uses 查, implying a read, but does not state whether the operation has side effects, what the blacklist entries contain, whether the result is paginated, or how the 'local' cache relates to server state. For a tool with zero annotation coverage, this is a significant gap.

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?

One compact sentence with no filler, and the filter capability is placed up front. Brevity here shades into under-specification rather than efficient exposition, but nothing written is wasted.

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?

No output schema and no annotations mean that the description must explain behavior, yet it barely does. It never says what a returned entry looks like or whether 'local' means a cached snapshot, and it offers no route to the sibling tools that mutate this list.

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?

The schema fully documents the single platform parameter, with an enum of bilibili or douyin and a description. The phrase 可按平台过滤 confirms that the parameter filters results and is optional, which matches the schema but adds little beyond it. With schema coverage at 100%, the baseline of 3 is appropriate.

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?

A specific verb and resource: 查 (query) plus 本地黑名单 (local blacklist). The qualifier 本地 distinguishes it from remote or platform-side blocking. It does not, however, contrast the tool with its siblings, such as unblock_author or get_audit, so an agent must infer the difference.

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 parenthetical 可按平台过滤 implies an optional filter but gives no guidance on when to choose this tool over the related siblings. It never says when not to use it, nor how it relates to unblock_author or block_author, so the agent has no routing signal.

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