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

新建短篇作品

create_short_story_qimao

Create a short story in the Qimao author backend by filling the new-story form with title, category, and content; preview first, then submit when confirm is enabled.

Instructions

在七猫作者后台的新建短篇页填表并可选提交。正文可用 content/file_path/article_id。经验字数区间 3000–100000 字(最佳 1 万 – 3 万字,以平台实际规则为准,本工具只提示不硬拦)。 ⚠️ 默认 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": {
      "title": "<title>"
    },
    "name": "create_short_story_qimao"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYes作品名称
confirmNo是否真正提交,默认 false
contentNo正文(与 file_path/article_id 三选一)
categoryNo作品分类名称
headlessNo是否无头运行,默认 true
file_pathNo正文文件路径(UTF-8 文本)
article_idNo本地文稿库 article_id(优先)

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 well: it discloses the dry-run default, that nothing is written without confirm=true, and that the word-count range is advisory only (提示不硬拦). It omits prerequisites such as login/auth and what is returned on submission.

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 sentences ordered by importance: action, content sources, advisory limits, then a prominent warning about the confirm default. Slight redundancy between '以平台实际规则为准' and '本工具只提示不硬拦', but nothing extraneous.

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 7-parameter mutation tool with no annotations and no output schema, the description covers the critical behavioral risk (accidental submission) and the content input modes. It stops short of describing what the tool returns on success or what auth state is required.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3; the description adds value beyond the schema by explaining the practical word-count range (3000–100000, sweet spot 10k–30k) and reinforcing that confirm=false means no write at all. Content-source precedence is only mirrored from the schema, not extended.

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?

States a concrete verb and resource: fill the 新建短篇 form on the Qimao author backend and optionally submit. The resource (short story) is distinctive enough to separate it from create_book_qimao, but no sibling is named explicitly, so differentiation is left implicit.

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?

Gives an explicit when-to-use rule through the confirm flag: confirm=false opens the page, reads current state and screenshots without filling or submitting; confirm=true fills and submits. It doesn't route the agent to alternatives such as publish_short_story_qimao or update_book_info_qimao when a short story already exists.

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