Skip to main content
Glama
Sign In
Storyblok MCP Server

Storyblok MCP Server

by Kiran1689
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

bulk_create_stories

Streamline content management by creating multiple stories in Storyblok simultaneously using an array-based input. Ideal for batch operations and efficient story generation.

Instructions

Creates multiple stories in 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": {
      "stories": "<stories>"
    },
    "name": "bulk_create_stories"
  }
}

Input Schema

NameRequiredDescriptionDefault
storiesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.5/5.0
Behavior1/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the action ('Creates') without detailing side effects, permissions needed, rate limits, or response format. This is inadequate for a mutation tool with zero annotation coverage.

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, efficient sentence with no wasted words. It is front-loaded and directly states the tool's action, making it highly concise and well-structured.

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

Completeness1/5

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

Given the complexity of a bulk creation tool with no annotations, 0% schema coverage, and no output schema, the description is severely incomplete. It lacks essential details on behavior, parameters, and outcomes, making it inadequate for effective tool use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description does not explain the 'stories' parameter beyond implying it's an array. It fails to specify what each story object should contain, such as required fields or structure, leaving parameters largely undocumented.

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 verb ('Creates') and resource ('multiple stories in Storyblok'), making the purpose specific and understandable. However, it does not explicitly differentiate from its sibling 'create_story' beyond the 'multiple' aspect, which is implied but not contrasted.

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 'create_story' or 'bulk_update_stories'. The description lacks context on prerequisites, such as required permissions or data format, leaving the agent without usage direction.

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