Skip to main content
Glama

List my decks

list_my_decks
Read-only

Lists the decks synced to the signed-in AnkiWeb account, parents before subdecks, with due counts and card totals. Use it to review your AnkiWeb deck structure and study workload.

Instructions

List the decks synced to the signed-in AnkiWeb account, parents before their subdecks, with due counts and card totals. Needs an AnkiWeb session.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_my_decks"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountNoOmit unless the user names an AnkiWeb account. Which of the accounts signed in on this machine to act as; a name that is not one is refused with the list.

Output Schema

NameRequiredDescriptionDefault
decksYes
currentDeckIdYes
mediaSizeBytesYes
collectionSizeBytesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.0.5
    • addedInput schema / properties / account
      Added value: +{
      +  "description": "Omit unless the user names an AnkiWeb account. Which of the accounts signed in on this machine to act as; a name that is not one is refused with the list.",
      +  "type": "string"
      +}
  2. First observedv0.0.2

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds real context beyond that: the hierarchical ordering (parents before subdecks), the presence of due counts and card totals in the result, and the session requirement — a genuine auth precondition the annotations do not convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, both front-loaded with the essential facts — scope first, prerequisite second. Nothing is redundant or padded.

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?

An output schema exists, so return values need not be enumerated; the description nonetheless flags the ordering and summary fields an agent will see. With the auth precondition stated and the sole parameter covered by schema, nothing needed 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 description coverage is 100%, and the single optional `account` parameter is documented thoroughly in the schema, including the refusal behaviour for unknown names. The description's only contribution is "signed-in account," which restates the schema's default, so the baseline 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?

The description gives a specific verb and resource ("List the decks") plus a clear scope: decks synced to the signed-in AnkiWeb account, parents before subdecks. The word "synced" implicitly separates it from the shared-deck siblings, though no 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?

It states a prerequisite ("Needs an AnkiWeb session") and implies the tool acts on the signed-in account rather than shared catalogues, but it never says when to prefer it over the shared-deck listing or search tools, or what to do when no session exists.

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