Skip to main content
Glama

update_asset_folder

Modify the name or parent folder of an existing asset folder in Storyblok by specifying a folder ID and optional new name or parent ID.

Instructions

    Update an existing asset folder's name or parent in the current Storyblok space.

    Parameters:
        folder_id (str): ID of the folder to update.
        name (Optional[str]): New name for the folder.
        parent_id (Optional[int]): New parent folder ID.

    Request Body Example:
        {
            "asset_folder": {
                "name": "Updated Folder",
                "parent_id": 456
            }
        }

    Returns:
        Dict[str, Any]: A success message or error content depending on response.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
folder_idYes
nameNo
parent_idNo
Behavior2/5

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

With no annotations provided, the description carries full burden. It states it's an update operation (implying mutation) and mentions the current Storyblok space context, but lacks critical behavioral details: permission requirements, whether changes are reversible, error handling, rate limits, or what 'success message or error content' entails. The request body example helps but doesn't fully compensate.

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?

Well-structured with clear sections (purpose, parameters, example, returns). Every sentence earns its place, but the returns statement is vague ('success message or error content') and could be more precise. Slightly front-loaded with the core purpose first.

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?

Given 3 parameters, no annotations, and no output schema, the description is moderately complete. It covers parameters well and provides an example, but lacks behavioral context (permissions, side effects) and output details. For a mutation tool with zero annotation coverage, it should do more to explain risks and responses.

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?

Schema description coverage is 0%, so the description must compensate fully. It explicitly lists all three parameters with types and semantics: folder_id as required ID, name as optional new name, and parent_id as optional new parent folder ID. The request body example further clarifies structure and usage, adding significant value beyond the bare schema.

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 action ('Update'), resource ('existing asset folder'), and scope ('in the current Storyblok space'), with specific attributes ('name or parent'). It distinguishes from create_asset_folder by specifying 'existing', but doesn't explicitly differentiate from other update tools like update_asset or update_component_folder.

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. It doesn't mention prerequisites (e.g., needing folder_id), when not to use it, or compare with sibling tools like update_asset or update_component_folder. The context is implied but not explicit.

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