Skip to main content
Glama

Get a shared deck

get_shared_deck
Read-only

Read an AnkiWeb shared deck's listing—description, tags, size, ratings, sample notes with media, and reviews—without an AnkiWeb session.

Instructions

Read a shared deck's AnkiWeb listing: description, tags, size, ratings, sample notes with their media, and reviews. Needs no AnkiWeb session. The notes, audio and images counts are AnkiWeb's own, and audio and images have been seen at 0 for a deck whose sample notes carry both.

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": {
      "deck": "<deck>"
    },
    "name": "get_shared_deck"
  }
}

Input Schema

NameRequiredDescriptionDefault
deckYesThe shared deck's id, or its https://ankiweb.net/shared/info/<id> link.
reviewsNoHow many of the newest reviews to include.

Output Schema

NameRequiredDescriptionDefault
idYes
urlYes
kindYes
tagsYes
audioNo
notesNo
titleYes
imagesNo
reviewsYesThe newest reviews, up to the number asked for.
updatedYes
thumbsUpYes
sizeBytesYes
supportUrlNo
thumbsDownYes
descriptionYesPlain text, with links written as [text](href).
reviewCountYes
sampleNotesYes
tooNewForRatingYes
originalDeckNameNo
itemsSharedByAuthorYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the readOnlyHint/openWorldHint annotations, the description adds two genuinely useful behavioral facts: no AnkiWeb session is required (an auth prerequisite), and AnkiWeb's own note/audio/image counts can be unreliable, having been observed as 0 for decks whose sample notes carry both. That data-quality caveat is exactly the kind of context annotations cannot convey.

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?

Three tight sentences with the payload listed up front and no filler. The final sentence is slightly convoluted in phrasing but earns its place by flagging a misleading data field.

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?

With an output schema present, the description does not need to explain return values, yet it still names the main sections an agent will receive. Auth requirements and the count-reliability caveat are covered; 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%, so both the deck identifier (id or info URL) and the reviews count are already documented in the schema. The description's mention of 'reviews' among returned fields is consistent but adds no syntax, defaults, or edge-case meaning beyond the structured definition.

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 opens with a specific verb and resource ('Read a shared deck's AnkiWeb listing') and enumerates exactly what the read returns: description, tags, size, ratings, sample notes with media, and reviews. This clearly separates it from download_shared_deck or search_shared_decks by implication, 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?

Usage is only implied - the agent can infer this is the inspection-before-download tool because it returns a listing rather than files, and 'Needs no AnkiWeb session' hints it works pre-auth. There is no explicit statement of when to prefer this over search_shared_decks or download_shared_deck, and no exclusions.

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