Skip to main content
Glama

List my shared decks

list_my_shared_decks
Read-only

List the decks you have shared on AnkiWeb, including download counts and ratings, using your signed-in session to review your published deck performance.

Instructions

List the decks the signed-in user has shared on AnkiWeb, with downloads and ratings. 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_shared_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
itemsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.0.5

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint; the description goes beyond them by disclosing that an AnkiWeb session is required and that results include downloads and ratings. That auth prerequisite is exactly the kind of context annotations cannot express, though nothing is said about result limits or ordering.

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 compact sentences with the resource scope front-loaded and the session prerequisite second; nothing is wasted or buried.

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?

An output schema exists so return values need not be explained, and for a single-optional-parameter read operation the description plus annotations cover what an agent needs. The only gap is the absence of routing guidance against the sibling deck-listing tools.

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's own account description already explains omission and the refusal behavior for unknown names, so the description need not duplicate it. Baseline 3 is appropriate since the description adds no parameter meaning beyond the schema.

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 ("List the decks the signed-in user has shared on AnkiWeb") and pins the scope to the signed-in user's own shares, which separates it in spirit from list_my_decks and search_shared_decks. It stops short of naming a sibling, so the differentiation must be inferred from phrasing rather than stated.

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 single sentence "Needs an AnkiWeb session" gives a prerequisite, which is real guidance, and the scope phrase implies when the tool applies. However, it never says when to choose search_shared_decks or get_shared_deck instead, and gives no exclusion conditions.

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