Skip to main content
Glama
Sign In
sameerbajaj

AnkiWeb MCP

by sameerbajaj
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Remote

learnings_list

Read-only

Lists recorded learnings from the local search_learnings table with filters for query, action, source, and confidence. Use it to review past teaching or manual-forget events.

Instructions

List recorded learnings from the local ankiweb search_learnings table

Input Schema

NameRequiredDescriptionDefault
csvNoOutput as CSV (table and array responses) (default: false)
yesNoSkip confirmation prompts (explicit confirmation for scripts) (default: false)
jsonNoOutput as JSON (default: false)
agentNoSet agent-friendly output defaults (--json --compact --no-input --no-color) (default: false)
limitNoMaximum rows to return (default: 200)
plainNoOutput as plain tab-separated text (default: false)
queryNoFilter by normalized query substring
quietNoBare output, one value per line (default: false)
actionNoFilter by action (boost | hide | alias_of)
selectNoComma-separated fields to include in output (e.g. --select id,notetype_id,deck_id)
sourceNoFilter by source (taught | manual-forget)
compactNoReturn only key fields (id, name, status, timestamps) for minimal token usage (default: false)
dry-runNoShow request without sending (default: false)
max-ageNoMaximum acceptable age of local-store data before a stderr hint suggests sync; 0 disables (default: 30m0s)
receiptNoWrite an atomic private run receipt (default: false)
timeoutNoRequest timeout (default: 1m0s)
no-cacheNoBypass response cache (default: false)
no-colorNoDisable colored output (default: false)
no-inputNoDisable all interactive prompts (for CI/agents) (default: false)
no-learnNoDisable the teach/recall learning loop for this invocation (default: false)
resourceNoFilter by resource_id
warningsNoReturn teach-time warnings from teach.log instead of stored learning rows (default: false)
idempotentNoTreat already-existing create results as a successful no-op (default: false)
rate-limitNoMax requests per second (0 to disable; default auto — pace to server rate-limit headers) (default: auto)
data-sourceNoData source for read commands: auto (live with local fallback), live (API only), local (synced data only) (default: auto)
client-profileNoSelect the tenant-gated client profile (env: ANKIWEB_CLIENT_PROFILE)
human-friendlyNoEnable colored output and rich formatting (default: false)
min-confidenceNoFilter by minimum confidence (default: 0)
allow-partial-failureNoDowngrade response-body partial-failure (e.g. partialFailureError) to a warning instead of a non-zero exit (default: false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already disclose readOnlyHint=true, destructiveHint=false, and openWorldHint=true. The description adds the useful detail that it reads from the local ankiweb search_learnings table, but does not explain notable behavioral flags such as warnings mode replacing rows or data-source fallback behavior.

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?

The description is a single efficient sentence with the resource and source table front-loaded. There is no filler or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Because the schema is fully documented and annotations cover the read-only safety profile, an agent can invoke the tool correctly. However, the description is thin for a 29-parameter tool and does not clarify the relationship to sibling learnings_* tools, which matters for correct selection.

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% across all 29 parameters, so the schema already explains flags like limit, warnings, data-source, and min-confidence. The description adds no parameter-specific semantics beyond what the schema provides, making the baseline 3 appropriate.

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 clear verb and resource: 'List recorded learnings' from a named table. It does not explicitly distinguish this from sibling tools like learnings_candidates or learnings_stats, so it falls short of a 5.

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

Usage Guidelines2/5

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

The description states what the tool does but gives no guidance on when to use it versus alternatives such as learnings_candidates, learnings_stats, or the mutation siblings. An agent must infer the selection criteria from tool names alone.

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