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

anki-connect-mcp

by SolarianGG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

notes.create

notes_create

Creates an Anki note using a specified note type, deck, and field values, then returns the actual cards generated from it.

Instructions

Create a note and return its actual generated cards.

Anki-Connect method notes.create. Scope: collection. Effect: write. Completion: completed. Undo: single.

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

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": {
      "noteType": "<noteType>",
      "deck": "<deck>",
      "fields": "<fields>"
    },
    "name": "notes_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
deckYesDeck: exactly one of {"id": "<deckId>"} or {"name": "<full deck name, e.g. Japanese::Verbs>"}.
tagsNoTags for the new note (no spaces inside a tag).
fieldsYesField values keyed by exact field name of the note type; values are HTML. Example: {"Front": "猫", "Back": "cat"}. For media, first call `media_store` and use the returned filename.
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.
noteTypeYesNote type: exactly one of {"id": "<noteTypeId>"} or {"name": "<note type name, e.g. Basic>"}.
duplicatesNoDuplicate policy {allow, scope: collection|deck, deck?}. Default: duplicates of the first field are rejected collection-wide.
rejectEmptyQuestionsNoFail if no card of the note would have a non-empty question. Default true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful context beyond that: collection scope, single-operation undo, completion state, and an enumerated error catalog including staleSession and editorConflict. It still does not say what happens on duplicate rejection by default (only the schema does) or whether a failed create leaves partial state.

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-loaded with the one-line purpose, followed by compact labeled metadata and an error list; almost every token carries information. The 'Anki-Connect method `notes.create`' line is largely redundant with the title and is the only clear waste.

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 7-parameter write tool with nested union objects and no output schema, the description covers the essentials: it says what is returned (generated cards), that it mutates the collection, that it is undoable as a single operation, and which errors to expect. Gaps are minor — no mention of the default duplicate rejection behavior or permission/session prerequisites beyond staleSession.

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 itself carries rich guidance (deck/noteType id-vs-name unions, session semantics, HTML field values, media_store prerequisite, duplicate policy default). The description adds no parameter-level meaning, so the baseline of 3 applies.

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 ('Create a note') and adds a non-obvious outcome ('return its actual generated cards'), which distinguishes it from a plain insert. It does not explicitly contrast with the close sibling notes_createMany or notes_validate, so sibling differentiation is only implied by the singular 'note'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance: nothing says to prefer notes_createMany for batches, to run notes_validate first, or to use editors_openAdd for interactive entry. The only usage-adjacent content is the metadata line (scope/effect/undo) and an error list, which describe behavior rather than selection criteria.

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