Skip to main content
Glama

删除永久素材

wechat_delete_material
Destructive

Deletes a specified permanent WeChat Official Account material by media_id; use when you need to remove stored assets, noting the action is irreversible and may invalidate draft covers that reference it.

Instructions

删除指定永久素材。此操作不可撤销,使用该素材的草稿封面可能失效。

Input Schema

NameRequiredDescriptionDefault
media_idYes素材 media_id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, so the base safety profile is covered. The description adds genuinely new behavioral context: the operation is irreversible and deleting a material may invalidate draft covers that reference it – a side effect not captured by any structured field.

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?

Two short sentences with zero filler; the action is stated first and the risk warning immediately follows. Every sentence carries distinct information.

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 single-parameter destructive tool with no output schema, the description covers what matters most: the target, irreversibility, and downstream impact on draft covers. It could mention permission requirements or behavior when the material is in use, but is otherwise sufficient to call safely.

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?

There is a single parameter with 100% schema description coverage ('素材 media_id'), so the schema fully documents it. The description adds no format hints, sourcing guidance, or examples beyond what the schema provides, which is the expected baseline for full coverage.

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 states a specific verb and resource ('删除指定永久素材'), making the target object unambiguous and implicitly distinct from sibling deletion tools like wechat_delete_draft. It stops short of explicitly naming those siblings, but an agent can identify the operation from the resource noun alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the destructive nature of the operation, and the irreversibility warning effectively signals 'only use when certain'. However, it never says how to obtain a media_id (e.g., via wechat_list_materials) or notes any preconditions before deletion, leaving the agent to infer the workflow.

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