Skip to main content
Glama

create_story

Creates a new story in Storyblok with support for all documented fields, including immediate publishing.

Instructions

Creates a new Storyblok story. Supports all documented fields including publishing.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesName of the story
slugYesURL slug of the story
contentYesStory content object
parent_idNoParent folder ID
group_idNoGroup ID
sort_by_dateNoSort by date field
is_folderNoWhether this is a folder
default_rootNoDefault root component
disable_fe_editorNoDisable frontend editor
is_startpageNoWhether this is the start page
meta_dataNoMeta data object
pinnedNoWhether the story is pinned
translated_slugs_attributesNoTranslated slug attributes
positionNoPosition in list
publishNoPublish immediately after creation
release_idNoRelease ID
Behavior2/5

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

With no annotations, the description carries full burden for behavioral disclosure. It only says 'creates' and 'supports all documented fields including publishing', but omits critical details like authentication needs, side effects, rate limits, or what happens on success/failure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

The description is a single sentence of 12 words, very concise and front-loaded with purpose. However, it may be too brief for such a complex tool, bordering on under-specification.

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?

Given the tool has 16 parameters, no output schema, and many sibling tools, the description is inadequate. It fails to explain return values, required fields, or post-creation behavior, leaving significant gaps for an agent to correctly invoke the tool.

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?

Schema coverage is 100% with descriptions for all 16 parameters. The description adds 'including publishing', emphasizing the publish parameter, but this adds minimal meaning beyond the schema. Baseline 3 is appropriate.

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 tool creates a new Storyblok story, with a specific verb and resource. It implies a single story creation, distinguishing it from the sibling bulk_create_stories tool, but does not explicitly differentiate.

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?

The description provides no guidance on when to use this tool versus alternatives like bulk_create_stories, create_story_schedule, or update_story. No when/when-not or prerequisite information is included.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

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