Skip to main content
Glama

Remove a shared listing

unshare_deck
DestructiveIdempotent

Remove a deck listing from AnkiWeb's shared catalogue, including its ratings and reviews, after a preview confirms. The deck in your own collection stays unchanged.

Instructions

Remove one of the signed-in user's listings from AnkiWeb's public shared-deck catalogue, with its ratings and reviews. It cannot be undone. The deck in the user's collection is not touched.

Without confirm, nothing is removed: the call finds the listing and returns a preview. Show that preview to the user and get their explicit go-ahead before calling again with confirm: true.

With more than one AnkiWeb account stored, the preview names the one the listing belongs to, and the confirmed call must name it in account.

Needs an AnkiWeb session.

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": {
      "listing": "<listing>"
    },
    "name": "unshare_deck"
  }
}

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.
confirmNotrue removes. Only after the user has seen the preview and agreed.
listingYesThe listing's shared id, its ankiweb.net/shared/info/<id> link, or its exact title, as list_my_shared_decks gives them.

Output Schema

NameRequiredDescriptionDefault
statusYes
accountNoThe account the listing belongs to, given when more than one is stored.
listingYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.0.5

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already flag destructive/openWorld/idempotent, but the description adds what they cannot: irreversibility, that the collection copy survives, that a dry-run preview is the default, the multi-account disambiguation rule, and the authentication prerequisite.

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?

Front-loaded with the destructive action and its irreversibility, then the safety protocol, then account handling. Slightly repetitive where it restates the schema's 'Only after the user has seen the preview and agreed', but every paragraph carries operational weight.

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 spelled out, and the preview behavior is nonetheless described. Combined with auth requirements and account selection, an agent has everything needed to call this destructive tool safely.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 100%, so the baseline is 3; the description earns extra by explaining the cross-parameter interaction — the preview names the owning account when several are stored and the confirmed call must then pass it in `account`, while `confirm` gates the actual mutation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a precise verb and resource ('Remove one of the signed-in user's listings from AnkiWeb's public shared-deck catalogue') plus the collateral scope (ratings and reviews). It also draws the crucial boundary against the deck-deletion sibling by declaring 'The deck in the user's collection is not touched.'

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit two-step protocol: without `confirm` the call is a non-destructive preview, and the agent must show that preview and obtain explicit user agreement before re-calling with `confirm: true`. It further conditions usage on an AnkiWeb session and on which account to name.

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