Skip to main content
Glama

duplicate_space

Duplicates an existing Storyblok space by specifying the original space ID and new space name. Supports optional configurations like domain, webhooks, and environments.

Instructions

Duplicates an existing Storyblok space via the Management API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
original_space_idYesID of the space to duplicate
new_space_nameYesName for the new duplicated space
domainNoDomain for the new space
story_published_hookNoWebhook URL for story published events
environmentsNoArray of environment configurations
searchblok_idNoSearchblok ID
has_pending_tasksNoWhether the space has pending tasks
Behavior2/5

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

No annotations, so description carries full burden. It only mentions 'via the Management API' but does not disclose what is duplicated (e.g., all content, settings), side effects, permissions, or whether it's synchronous. Insufficient for a complex operation.

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?

One sentence with no extraneous words. Highly concise and front-loaded with key action and object.

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?

Despite 7 parameters and no output schema, the description provides minimal context. Lacks details on what is duplicated, result format, or constraints, making it insufficient for an agent to fully understand the 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. Description adds no extra parameter meaning, such as how domain or environments affect the duplication.

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 action ('Duplicates') and the resource ('existing Storyblok space'), differentiating it from siblings like create_space (creates new) and backup_space (backup).

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 on when to use duplicate versus creating a new space or backing up. The description does not mention prerequisites, limitations, or alternatives.

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