Skip to main content
Glama

create_asset_folder

Create and organize asset folders in Storyblok spaces by specifying a name and optional parent folder ID. Simplifies asset management for streamlined workflows.

Instructions

    Create a new asset folder in the current Storyblok space.

    Parameters:
        name (str): Name of the new asset folder.
        parent_id (Optional[int]): ID of the parent folder (if nested).

    Request Body Example:
        {
            "asset_folder": {
                "name": "My Folder",
                "parent_id": 123
            }
        }

    Returns:
        Dict[str, Any]: The API response with created folder info or an error message.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
parent_idNo
Behavior3/5

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

With no annotations provided, the description carries the full burden. It correctly identifies this as a creation operation (implying mutation) and mentions the Storyblok space context, but lacks details on permissions, rate limits, error handling, or whether the operation is idempotent. It provides basic behavioral context but misses important operational details for a mutation tool.

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 well-structured with clear sections (purpose, parameters, example, returns) and uses minimal sentences. The request body example is helpful but slightly verbose; overall it's efficient with good information density.

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

Completeness3/5

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

For a mutation tool with no annotations and no output schema, the description provides adequate basic information (purpose, parameters, example) but lacks important context about permissions, error responses, space requirements, or how the created folder integrates with other operations. It's minimally viable but has clear gaps for a creation tool.

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

Parameters5/5

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

With 0% schema description coverage, the description fully compensates by clearly explaining both parameters: 'name' as the folder name and 'parent_id' as optional nesting with an example. It adds significant value beyond the bare schema, providing practical usage context and formatting guidance.

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 specific action ('Create a new asset folder') and resource ('in the current Storyblok space'), distinguishing it from sibling tools like 'create_component_folder' or 'create_space' by specifying the asset folder context. It provides a complete verb+resource+scope statement.

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 'update_asset_folder' or 'retrieve_asset_folders', nor does it mention prerequisites such as required permissions or space context. It lacks explicit when/when-not instructions or sibling comparisons.

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

Related 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/Kiran1689/storyblok-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server