delete_story
Delete a story from Storyblok by providing its unique ID.
Instructions
Deletes a story by ID.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | ID of the story to delete |
Delete a story from Storyblok by providing its unique ID.
Deletes a story by ID.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | ID of the story to delete |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided. Description does not disclose whether deletion is permanent, soft delete, or any side effects. For a destructive operation, this is a significant gap.
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?
Single, direct sentence with no extraneous words. Front-loads action and resource efficiently.
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?
Despite low complexity, the description omits critical context such as irreversibility, permissions, or whether it triggers cascading deletes. No output schema or annotations to compensate.
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 covers 100% of parameters and includes a description for 'id'. The tool description adds no additional meaning beyond what the schema already provides, so baseline score is appropriate.
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 explicitly states the action ('deletes') and resource ('story') and indicates the parameter ('by ID'). It clearly distinguishes from sibling tools like 'delete_story_schedule' or 'bulk_delete_stories'.
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 on when to use this tool versus alternatives such as 'bulk_delete_stories' or prerequisites like required permissions or impact on related entities.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/hypescale/storyblok-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server