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

anki-connect-mcp

by SolarianGG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

notes.getMany

notes_getMany
Read-only

Retrieve multiple Anki notes by their IDs in the exact input order, including repeated IDs, for batch lookups or syncing note data.

Instructions

Get notes in input order, preserving repeated IDs.

Anki-Connect method notes.getMany. Scope: collection. Effect: read. Completion: completed. Undo: none.

Possible errors: collectionUnavailable, 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_getMany"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYesNote IDs (decimal string, e.g. "1700000000001"); results keep input order, including repeats.
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.8/5.0
Behavior4/5

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

Annotations already cover readOnly/openWorld/destructive, so the description correctly focuses on additions: scope (collection), completion semantics, no undo, and an enumerated error set including `staleSession` and `notFound`. What is not clarified is whether one missing ID fails the whole batch or yields partial results.

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 ordering guarantee is front-loaded in the first sentence and the metadata block is compact. Minor waste: 'Effect: read' duplicates `readOnlyHint` and the Anki-Connect method name repeats the tool name.

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 two-parameter read tool with full schema coverage and no output schema, this covers scope, ordering, safety, and failure modes. Nothing essential for a correct call is missing.

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 coverage is 100% and both parameters are well documented there, including the session rationale, so the baseline of 3 applies. The description's order/repeat note largely restates the schema's own `ids` description rather than adding new meaning.

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 (get notes) plus a distinguishing behavioral trait: input order is preserved and repeated IDs are retained. That separates it from the singular `notes_get` and from `notes_search`, though neither sibling is named explicitly.

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?

Usage is only implied: an agent infers it should call this when it already has a list of note IDs. There is no explicit statement about when to prefer `notes_get` or `notes_search` instead, and no note on batch-size limits.

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