Skip to main content
Glama

create_space_role

Create a custom space role in Storyblok by defining permissions, allowed paths, field access, and other controls.

Instructions

Creates a new custom space role with specific permissions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
role_nameYesName of the role
permissionsYesArray of permission strings
allowed_pathsNoArray of allowed path IDs
field_permissionsNoArray of field permission strings
readonly_field_permissionsNoArray of readonly field permission strings
subtitleNoSubtitle for the role
datasource_idsNoArray of allowed datasource IDs
component_idsNoArray of allowed component IDs
branch_idsNoArray of allowed branch IDs
allowed_languagesNoArray of allowed language codes
asset_folder_idsNoArray of allowed asset folder IDs
Behavior2/5

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

No annotations provided; description implies mutation but lacks details on permissions needed, idempotency, or side effects.

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

Conciseness3/5

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

One sentence is concise but too minimal; could include more value without being 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?

No output schema and no details on return value, immediate effects, or required permissions; incomplete for a complex tool with 11 parameters.

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 description coverage is 100%, so the schema already explains parameters; description adds no extra meaning beyond 'specific permissions'.

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 ('Creates') and the resource ('custom space role with specific permissions'), differentiating it from siblings like update_space_role and delete_space_role.

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 this tool versus alternatives; no prerequisites or conditions 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