get_statsGet collection statistics including progress, rating distribution, genre/theme breakdown, and timeline. If no media_type specified, returns combined stats.
| Name | Required | Description | Default |
|---|---|---|---|
| media_type | No | Type of media (optional - omit for all) |
| Name | Required | Description | Default |
|---|---|---|---|
| by_rating | No | ||
| by_status | No | ||
| top_genres | No | ||
| top_themes | No | ||
| total_items | Yes | ||
| by_media_type | No |
Changes observed during successful MCP inspections.
Input schema / properties / media_type / enumPrevious value: -[
- "book",
- "movie",
- "album",
- "show",
- "anime"
-]New value: +[
+ "book",
+ "movie",
+ "album",
+ "show",
+ "anime",
+ "podcast",
+ "game",
+ "manga"
+]Output schema / (root)Previous value: -nullNew value: +{
+ "additionalProperties": true,
+ "description": "Aggregate statistics for the user's collection.",
+ "properties": {
+ "by_media_type": {
+ "additionalProperties": true,
+ "properties": {
+ "albums": {
+ "type": "number"
+ },
+ "anime": {
+ "type": "number"
+ },
+ "books": {
+ "type": "number"
+ },
+ "games": {
+ "type": "number"
+ },
+ "movies": {
+ "type": "number"
+ },
+ "podcasts": {
+ "type": "number"
+ },
+ "shows": {
+ "type": "number"
+ }
+ },
+ "type": "object"
+ },
+ "by_rating": {
+ "additionalProperties": {
+ "type": "number"
+ },
+ "type": "object"
+ },
+ "by_status": {
+ "additionalProperties": {
+ "type": "number"
+ },
+ "type": "object"
+ },
+ "top_genres": {
+ "items": {
+ "additionalProperties": true,
+ "properties": {
+ "count": {
+ "type": "number"
+ },
+ "genre": {
+ "type": "string"
+ }
+ },
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "top_themes": {
+ "items": {
+ "additionalProperties": true,
+ "properties": {
+ "count": {
+ "type": "number"
+ },
+ "theme": {
+ "type": "string"
+ }
+ },
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "total_items": {
+ "type": "number"
+ }
+ },
+ "required": [
+ "total_items"
+ ],
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered. The description adds the aggregation behavior (combined stats when media_type is omitted), which is genuinely useful, but the enumerated stat categories largely restate what the existing output schema likely documents.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two tight sentences, no filler. The content list comes first and the default-behavior caveat follows, so the agent gets the essentials immediately.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a one-parameter read tool with an output schema and full annotation coverage, the description supplies what an agent needs to call it correctly. Only the lack of sibling routing guidance keeps it short of complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% and the single parameter has an enum plus an inline "optional - omit for all" description. The description's note about combined stats when media_type is absent adds only slight meaning beyond what the schema already conveys.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb (Get) and resource (collection statistics) and enumerates the stat categories returned: progress, rating distribution, genre/theme breakdown, timeline. It is clearly distinguishable from mutation siblings, though it does not explicitly separate itself from read siblings like get_timeline or get_by_rating whose names overlap with the listed stat types.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
"If no media_type specified, returns combined stats" gives a usable default-behavior hint, but there is no explicit guidance on when to use this aggregate tool versus per-dimension siblings such as get_by_rating, get_by_status, or get_timeline. Usage is implied rather than stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.