Skip to main content
Glama

保存到秀米

xiumi_save

Save the current Xiumi article to your account, with login required, and return whether the save succeeded plus a status message.

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": "xiumi_save"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose two useful traits: an auth prerequisite and that the result is a success flag plus a message. It does not say whether saving overwrites or versions existing content, whether it is destructive, or what happens on failure — meaningful gaps for a mutation tool.

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, front-loaded with the action and target, then the login prerequisite, then the return shape. No filler or restatement of the title beyond what is needed.

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?

There is no output schema, and the description partly compensates by describing the return as success plus message. For a zero-parameter but stateful write operation with no annotations, however, it omits prerequisite state (must an article be open?) and side effects on existing saved content, leaving real ambiguity about when the call will work.

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?

The tool takes zero parameters, which is the baseline-4 case. The empty schema leaves nothing to misinterpret, and the description correctly implies the target is the currently open article rather than an ID argument.

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 specific verb and resource: save the current article ('图文') to the Xiumi account. An agent can tell this is the persistence step, distinct from siblings that edit content (xiumi_fill_text, xiumi_set_meta) or read data (xiumi_get_html). It does not explicitly name a sibling it is not, so it stops short of 5.

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?

Includes one real usage condition — '需登录' (login required) — which implies xiumi_login must come first. However, it says nothing about ordering relative to xiumi_start/xiumi_open_article, or what to do instead if the user does not want to persist. Usage is implied rather than spelled out.

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