Skip to main content
Glama

update_space

Update a Storyblok space's name, domain, owner, webhooks, and other settings by its space ID.

Instructions

Updates an existing Storyblok space via the Management API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
space_idYesID of the space to update
nameNoNew name for the space
domainNoNew domain
uniq_domainNoUnique domain
owner_idNoOwner user ID
story_published_hookNoWebhook URL for story published events
environmentsNoArray of environment configurations
parent_idNoParent space ID
searchblok_idNoSearchblok ID
duplicatableNoWhether the space can be duplicated
billing_addressNoBilling address object
routesNoArray of routes
default_rootNoDefault root content type
has_pending_tasksNoWhether the space has pending tasks
ai_translation_disabledNoWhether AI translation is disabled
optionsNoAdditional options
Behavior2/5

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It only says 'Updates' without detailing side effects, required permissions, destructive nature, or partial update behavior. Important traits are missing.

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 with no wasted words. It efficiently states the core purpose, though it could be slightly expanded with key context without becoming verbose.

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 16 parameters, no output schema, and no annotations, the description is too minimal. It does not explain return values, error handling, or typical usage patterns, making it inadequate for a complex operation.

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%, so baseline is 3. The description does not add additional meaning beyond the schema; some parameters like 'uniq_domain' or 'environments' could benefit from explanation, but the schema descriptions are present.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Updates', the resource 'existing Storyblok space', and the context 'via the Management API'. This effectively distinguishes it from sibling tools like create_space or delete_space.

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, such as whether the space must exist or that create_space should be used for new spaces. No prerequisites or exclusions are mentioned.

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