Skip to main content
Glama
Sign In
Storyblok MCP Server

Storyblok MCP Server

by Kiran1689
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

delete_asset

Remove unwanted assets directly from Storyblok by specifying the asset ID using this tool. Simplify asset management within your Storyblok spaces.

Instructions

Deletes an asset from Storyblok.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "delete_asset"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the basic action. It doesn't disclose critical behavioral traits such as whether deletion is permanent or reversible, what permissions are required, if there are confirmation prompts, rate limits, or what happens to dependent content. 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, direct sentence with no wasted words. It's front-loaded and efficiently communicates the core action without unnecessary elaboration.

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

Completeness2/5

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

For a destructive tool with no annotations, no output schema, and minimal parameter documentation, the description is inadequate. It doesn't cover safety considerations, error conditions, or result expectations, leaving the agent with insufficient context for reliable use.

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?

The schema has 0% description coverage, but the parameter 'id' is self-explanatory. The description doesn't add any parameter details beyond what's implied by the tool name. Since there's only one parameter, the baseline is 4, but the lack of any guidance on ID format or sourcing reduces it to 3.

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 clearly states the action ('Deletes') and resource ('an asset from Storyblok'), making the purpose unambiguous. However, it doesn't differentiate from sibling tools like 'delete_multiple_assets' or 'delete_asset_folder', which would require specifying this is for single assets only.

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?

No guidance is provided on when to use this tool versus alternatives like 'delete_multiple_assets' for bulk operations or 'delete_asset_folder' for folders. The description lacks context about prerequisites, permissions, or typical use cases.

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

Related Tools