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

anki-connect-mcp

by SolarianGG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

media.list

media_list
Read-only

List normalized Anki media basenames matching a basename glob, such as *.mp3, to locate stored media files by name pattern.

Instructions

List normalized media basenames matching a basename glob.

Anki-Connect method media.list. Scope: collection. Effect: read. Completion: completed. Undo: none.

Possible errors: collectionUnavailable, internalError, invalidParams, staleSession.

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": "media_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
patternNoBasename glob, e.g. `*.mp3`. Default `*`.*
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.9/5.0
Behavior4/5

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

Annotations already declare readOnly, non-destructive, and closed-world, so the bar is lower, yet the description still contributes: scope (collection), undo: none, completion state, and an enumerated error set including staleSession and collectionUnavailable. It stops short of saying what the returned basenames look like or whether results are sorted or bounded.

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?

One front-loaded sentence states the action, followed by compact labelled metadata lines (Scope, Effect, Completion, Undo) and an error list. Nearly every token carries information; only the redundant restatement of the method name in 'Anki-Connect method `media.list`' is arguably filler.

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?

For a zero-required-parameter read tool with full schema coverage and no output schema, the definition supplies scope, effect, undo semantics, and error modes — enough to call it correctly. The main gap is the shape of the result (list of basename strings, ordering, empty-collection behavior), which the absence of an output schema leaves unspecified.

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 100%, so the baseline is 3, but the description reinforces the key semantic constraint — that `pattern` matches basenames, not paths — which is the main misreading risk the schema's regex alone doesn't make obvious. The `session` parameter's meaning is left entirely to 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?

The description opens with a specific verb and resource: 'List normalized media basenames matching a basename glob.' The 'basename glob' qualifier separates it conceptually from path-oriented siblings like media_getDirectory, though neither that tool nor media_get/media_store is named explicitly, so a reader must infer the boundary.

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 default `*` and the example `*.mp3` show how to call it, and 'Scope: collection' hints at the target, but there is no statement of when to prefer this over media_getDirectory or media_get, and no when-not guidance.

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