anki-mcp-server

Overview Schema Source Related Servers Discussions Admin

Delete notes

anki_delete_notes

Destructive

Delete Anki notes with their cards and review history by note IDs or a search query. Preview and confirm the deletion, with a JSON backup written first.

Instructions

Delete notes with all their cards and review history. Give note_ids OR an Anki search query. Two-step: preview + token, then call again with confirm_token. A JSON backup is written first.

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

Input Schema

Name	Required	Description	Default
`query`	No
`note_ids`	No
`confirm_token`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Nov 4, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, and the description goes further by disclosing the blast radius (cards and full review history are destroyed), the safety mechanism (a JSON backup is written first) and the required two-step confirmation. That is precisely the extra context an agent needs before committing to an irreversible operation.

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?

Three short sentences, front-loaded with the destructive action and cascade, followed by parameter usage and the approval flow. Nothing is repeated and every clause carries operational 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 destructive three-parameter tool with an output schema and strong annotations, the description covers the essential workflow and data-safety story. It leaves the preview response contents and error behavior for an invalid or expired confirm_token to the output schema and annotations.

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 description coverage is 0%, so the description must carry the parameters, and it does: note_ids and query are framed as mutually exclusive alternatives, and confirm_token is explained as the value obtained from the preview step. It does not hint at the expected Anki query syntax or array format, which is a minor remaining gap.

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 and resource plus its side effect: deletes notes together with all their cards and review history. That cascade detail is what separates it cleanly from siblings like anki_update_notes, anki_move_notes and anki_delete_deck.

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?

Tells the agent exactly how to invoke it: provide note_ids OR an Anki search query, and follow a two-step preview-token-then-confirm flow. It never explicitly says when to prefer a search query over explicit IDs or which sibling to use instead, so it stops short of full when/when-not guidance.

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

Deploy Server