Skip to main content
Glama
Sign In
sameerbajaj

AnkiWeb MCP

by sameerbajaj
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Remote

card_import

Destructive

Batch import flashcards from Markdown files, Q&A blocks, and cloze notes into any Anki deck, with configurable tags, notetype, and output format.

Instructions

Batch import flashcards from Markdown files, Q&A blocks, and cloze notes into any deck.

Input Schema

NameRequiredDescriptionDefault
csvNoOutput as CSV (table and array responses) (default: false)
yesNoSkip confirmation prompts (explicit confirmation for scripts) (default: false)
deckNoTarget deck name or ID (default: Default)
fileNoMarkdown file path to import (or '-' for stdin)
jsonNoOutput as JSON (default: false)
tagsNoDefault tags to apply to all imported cards
agentNoSet agent-friendly output defaults (--json --compact --no-input --no-color) (default: false)
plainNoOutput as plain tab-separated text (default: false)
quietNoBare output, one value per line (default: false)
selectNoComma-separated fields to include in output (e.g. --select id,notetype_id,deck_id)
compactNoReturn only key fields (id, name, status, timestamps) for minimal token usage (default: false)
dry-runNoShow request without sending (default: false)
max-ageNoMaximum acceptable age of local-store data before a stderr hint suggests sync; 0 disables (default: 30m0s)
receiptNoWrite an atomic private run receipt (default: false)
timeoutNoRequest timeout (default: 1m0s)
no-cacheNoBypass response cache (default: false)
no-colorNoDisable colored output (default: false)
no-inputNoDisable all interactive prompts (for CI/agents) (default: false)
no-learnNoDisable the teach/recall learning loop for this invocation (default: false)
notetypeNoDefault notetype for imported cards (default: Basic)
idempotentNoTreat already-existing create results as a successful no-op (default: false)
rate-limitNoMax requests per second (0 to disable; default auto — pace to server rate-limit headers) (default: auto)
data-sourceNoData source for read commands: auto (live with local fallback), live (API only), local (synced data only) (default: auto)
client-profileNoSelect the tenant-gated client profile (env: ANKIWEB_CLIENT_PROFILE)
human-friendlyNoEnable colored output and rich formatting (default: false)
allow-partial-failureNoDowngrade response-body partial-failure (e.g. partialFailureError) to a warning instead of a non-zero exit (default: false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations declare destructiveHint=true and openWorldHint=true, so an agent knows this mutates state, yet the description says nothing about what is destroyed or created, duplicate handling, confirmation prompts, or rollback. Those details exist only as opaque flags (`yes`, `idempotent`, `dry-run`) in the schema, leaving the description to add almost nothing beyond annotations.

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?

A single front-loaded sentence with no filler or redundancy. It is efficient, though for a 26-parameter destructive tool the brevity is arguably under-specification rather than optimal conciseness.

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

Completeness2/5

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

With 26 optional parameters, destructive semantics, and no output schema, an agent needs to know what the import produces (counts, errors, partial failures) and how to invoke it safely. The description covers none of this, leaving critical behavior to flag names alone.

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%, so baseline 3 applies; every one of the 26 parameters is already documented in the schema. The description only implies `deck` and source-format semantics, adding no format syntax or naming conventions beyond the structured data.

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 ('Batch import flashcards') and enumerates the accepted source formats (Markdown files, Q&A blocks, cloze notes) plus the destination ('any deck'). It is clear on its own, but never names how it differs from the sibling `import` or `card_add`, which an agent would want to disambiguate.

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 guidance on when to choose this over `card_add` (single card) or the generic `import` sibling, nor any mention of prerequisites such as confirmation handling or dry-run. The only usage signal is the implicit 'batch' qualifier.

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