Skip to main content
Glama
Sign In
anki-connect-mcp

anki-connect-mcp

by SolarianGG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

deckPresets.delete

deckPresets_delete
Destructive

Delete an Anki deck options preset; if decks still use it, provide a replacement preset to reassign them first.

Instructions

Delete a preset, explicitly reassigning dependent decks first.

replacement is required when in use. Reject Default preset deletion. No changes occur on failed preflight; do not promise atomicity across multiple native backend operations.

Anki-Connect method deckPresets.delete. Scope: collection. Effect: write. Completion: operation. Undo: grouped.

Long-running operation: by default the server waits for the final result (see waitForCompletion / timeoutSeconds).

Possible errors: collectionUnavailable, conflict, editorConflict, internalError, invalidParams, notFound, staleSession.

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": {
      "preset": "<preset>"
    },
    "name": "deckPresets_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
presetYesDeck options preset: exactly one of {"id": "<presetId>"} or {"name": "<preset name>"}.
sessionNoOptional. Collection session ID: the `session` field returned by `collection_get`. Usually omit it — the server then uses the session current at the time of the call. Pass it to make the call fail with `staleSession` instead of acting on a different profile/collection than the one your IDs, cursors and tokens came from.
replacementNoPreset for decks that use the deleted one: exactly one of {"id": "<presetId>"} or {"name": "<preset name>"}. Required if the preset is in use.
timeoutSecondsNoMCP option (not sent to Anki): how long to wait for completion. A timeout does not cancel the work; the pending record is returned.
waitForCompletionNoMCP option (not sent to Anki): poll operations.get until the operation finishes and return its final record. If false, return the operation handle.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Beyond destructiveHint=true, the description discloses that failed preflight leaves state unchanged, that atomicity across multiple native backend operations should not be promised, that undo is grouped, that scope is collection-level, and it lists the possible error codes. That is exactly the behavioral context annotations cannot carry.

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?

Front-loads the purpose in the first sentence, then compresses constraints, async behavior, and error surface into short clauses with no filler. The staccato fragment style is terse but each line carries a distinct fact.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, long-running, no-output-schema tool, the definition covers preconditions, failure semantics, undo grouping, async waiting, and the error envelope. Nothing an agent needs to invoke it safely is missing.

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 the baseline is 3; the description adds meaning by framing replacement as an explicit reassignment step that must precede deletion and by pointing to waitForCompletion/timeoutSeconds for the async behavior. It does not restate the id-vs-name selector, which is already fully documented in the schema.

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 ("Delete a preset") plus the distinctive ordering constraint ("explicitly reassigning dependent decks first"). No sibling tool in the list performs deletion of deck presets, so the agent can identify it unambiguously.

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 concrete preconditions: replacement is required when the preset is in use, and the Default preset cannot be deleted. It does not name alternative tools or paths (e.g. deckPresets_assign for a pure reassignment), so it stops short of explicit when-to-use-vs-alternative routing.

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

Deploy Server

Other Tools