Storyblok MCP Server

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

No annotations are provided, so the description carries full burden. It states 'Deletes', implying a destructive mutation, but doesn't disclose behavioral traits like whether deletion is permanent, requires specific permissions, or has side effects (e.g., affecting associated stories). This leaves significant gaps for a mutation tool, scoring 2 due to inadequate disclosure beyond the basic action.

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?

The description is a single, efficient sentence that front-loads the core action ('Deletes a preset') and includes necessary context ('from a Storyblok space using the Management API'). There is no wasted wording, making it appropriately sized and well-structured, earning a 5.

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?

Given the complexity of a deletion tool with no annotations and no output schema, the description is incomplete. It lacks details on behavioral aspects (e.g., permanence, permissions), usage prerequisites, and expected outcomes. For a destructive operation, this minimal description is insufficient, scoring 2 as it fails to compensate for the missing structured data.

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%, with the parameter 'preset_id' fully documented in the schema as 'Numeric ID of the preset to delete'. The description adds no additional parameter information beyond what the schema provides, so it meets the baseline of 3 for high schema coverage without extra value.

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?

The description clearly states the action ('Deletes') and the resource ('a preset from a Storyblok space'), and specifies the API used ('Management API'). It distinguishes from siblings like 'delete_story' or 'delete_asset' by focusing on presets. However, it doesn't explicitly differentiate from 'delete_multiple_presets' (which doesn't exist) or other deletion tools, keeping it at 4 instead of 5.

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?

No guidance is provided on when to use this tool versus alternatives. For example, it doesn't mention prerequisites (e.g., needing a preset ID from 'retrieve_single_preset' or 'retrieve_multiple_presets'), or warn about irreversible deletion. The description is standalone without context, scoring 2 for lack of usage instructions.

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