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

anki-connect-mcp

by SolarianGG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

notes.delete

notes_delete
Destructive

Delete Anki notes and their associated cards by note ID, returning item-level errors for missing IDs.

Instructions

Delete notes and their cards; missing IDs are item errors.

Anki-Connect method notes.delete. Scope: collection. Effect: write. Completion: completed. Undo: perItem.

Possible errors: collectionUnavailable, 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": {
      "ids": "<ids>"
    },
    "name": "notes_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYesNote IDs to delete together with their cards (decimal string, e.g. "1700000000001").
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the destructiveHint/readOnlyHint annotations, the description discloses cascade behavior (cards are deleted with notes), partial-success semantics ('missing IDs are item errors'), per-item undo granularity, and the concrete error vocabulary (collectionUnavailable, editorConflict, staleSession, etc.). It stops short of stating irreversibility or whether item errors leave other IDs deleted, which would be the final useful detail.

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?

The first sentence carries the core semantics and the metadata lines are labeled and scannable; nothing is padded prose. The possible-errors list is somewhat boilerplate-heavy but is structured rather than wasteful.

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?

With no output schema, the description still conveys result semantics through 'missing IDs are item errors' and 'Undo: perItem', and the error enumeration tells the agent what failure modes to handle. What's missing is any statement of what a successful response contains (e.g., deleted vs. failed ID lists).

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

Parameters3/5

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

Schema description coverage is 100%, and the schema already explains both `ids` (decimal string, cascading card deletion) and the optional `session` stale-session behavior thoroughly. The description adds nothing about parameters beyond that, so baseline 3 applies.

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 notes and their cards') and immediately adds a consequence the name alone doesn't carry — that cards are removed too. This clearly separates it from read-side siblings like notes_get, notes_search, and from notes_update.

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?

The scope/effect/completion lines imply this is a collection-scoped write, which helps orient the agent, but there is no explicit 'use this when…' or 'prefer X instead' guidance relative to siblings such as notes_findEmpty, notes_update, or collection_undo. The undo hint gives a recovery path but not a selection rule.

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