bulk_delete_stories
Delete multiple Storyblok stories at once by passing an array of story IDs.
Instructions
Deletes multiple stories in Storyblok.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| story_ids | Yes | Array of story IDs to delete |
Delete multiple Storyblok stories at once by passing an array of story IDs.
Deletes multiple stories in Storyblok.
| Name | Required | Description | Default |
|---|---|---|---|
| story_ids | Yes | Array of story IDs to delete |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided; description only states the action without disclosing consequences, auth needs, rate limits, or error handling for a destructive operation.
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, efficient sentence with no superfluous information.
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?
Lacks details on return value, partial success behavior, or potential errors; incomplete for a high-importance delete tool with no output schema.
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 has 100% description coverage, so baseline 3; description adds no extra meaning beyond the schema's 'Array of story IDs to delete'.
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?
Clearly states the verb 'deletes' and resource 'multiple stories', effectively distinguishing from sibling tools like delete_story and bulk_create_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?
Implies batch deletion but provides no explicit guidance on when to use vs alternatives like delete_story, or any prerequisites or limits.
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