delete-notebook
Delete a notebook from your Evernote account by providing its GUID, confirmation flag, and confirmation GUID.
Instructions
删本
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| guid | Yes | ||
| force | No | ||
| confirm | Yes | ||
| confirmGuid | Yes |
Delete a notebook from your Evernote account by providing its GUID, confirmation flag, and confirmation GUID.
删本
| Name | Required | Description | Default |
|---|---|---|---|
| guid | Yes | ||
| force | No | ||
| confirm | Yes | ||
| confirmGuid | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, and the description does not disclose any behavioral traits such as whether deletion is permanent, what authorization is needed, or what side effects occur. For a destructive action, this is insufficient.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
While extremely concise at one word, the description sacrifices all meaningful content. Conciseness should support clarity, not replace it.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the destructive nature, four parameters (three required), and a rich set of sibling tools, the description is completely inadequate. No output schema is provided, and no context is added beyond the tool name.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The description '删本' adds no meaning beyond the input schema. With 0% schema description coverage, all four parameters (guid, force, confirm, confirmGuid) remain unexplained, leaving the agent without guidance on how to invoke the tool correctly.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description '删本' is a tautology, essentially restating the tool name 'delete-notebook' in Chinese. It fails to specify what a 'notebook' is or how this differs from sibling tools like delete-note or delete-stack.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives like delete-note, delete-stack, or remove-notebook-from-stack. The description gives no context for appropriate usage.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/ArchChuan/yinxiang-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server