Skip to main content
Glama
qimao-autopub-mcp
by yangmi829

删除短篇作品 / 草稿

delete_short_story_qimao

Preview and permanently delete a specified Qimao short story or draft by book_id; use confirm=false for a safe preview and confirm=true to execute deletion.

Instructions

删除指定短篇作品或草稿(破坏性)。默认 confirm=false 只预览;confirm=true 才真正删除。

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": {
      "book_id": "<book_id>"
    },
    "name": "delete_short_story_qimao"
  }
}

Input Schema

NameRequiredDescriptionDefault
book_idYes短篇 book_id
confirmNo是否真正删除,默认 false
headlessNo是否无头运行,默认 true

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/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 burden and does disclose the most important trait: it is destructive and defaults to a non-destructive preview (confirm=false), only deleting when confirm=true. It still omits whether deletion is reversible, what permissions are needed, and what the preview returns.

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 the destructive warning front-loaded and the confirm behavior immediately after. No filler, and the highest-risk information appears first.

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 destructive 3-parameter tool with no annotations and no output schema, the safety-critical behavior is covered. Minor gaps remain around reversibility and the preview payload, but an 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 description coverage is 100%, so book_id, confirm and headless are already documented; the description's confirm explanation largely repeats the schema text. Baseline 3 is appropriate since the schema does the heavy lifting.

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 specific verb (删除) plus the exact resource (短篇作品或草稿), which cleanly separates it from the sibling delete_chapter_qimao and delete_article tools. An agent can pick this tool without inspecting the schema.

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 tag and the confirm flow, but the description never says when to choose this over the sibling delete tools or what preconditions apply. The confirm semantics read as parameter behavior rather than selection guidance.

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