Skip to main content
Glama

retrieve_asset_folders

Access and filter asset folders from a Storyblok space by name, parent ID, specific folder IDs, or UUIDs to streamline content organization and management.

Instructions

    Retrieve a list of asset folders from the current Storyblok space.

    Parameters:
        search (Optional[str]): A search query to filter asset folders by name.
        with_parent (Optional[int]): ID of the parent folder to filter results.
        by_ids (Optional[List[int]]): Specific folder IDs to fetch.
        by_uuids (Optional[List[str]]): Specific folder UUIDs to fetch.

    Returns:
        Any: The API response with a list of asset folders or an error message.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
by_idsNo
by_uuidsNo
searchNo
with_parentNo
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It indicates this is a read operation ('Retrieve'), but lacks details on permissions, rate limits, pagination, or error handling. The mention of 'API response' hints at external behavior, but remains vague. It adds minimal behavioral context beyond the basic action.

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?

The description is well-structured and front-loaded with the core purpose, followed by a clear parameter list and return statement. Every sentence adds value without redundancy, and it avoids unnecessary elaboration, making it efficient for quick understanding.

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 the tool's moderate complexity (4 parameters, no output schema, no annotations), the description is partially complete. It covers the purpose and parameters adequately but lacks behavioral details like error handling, pagination, or usage context, leaving gaps for an AI agent to infer.

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

Parameters4/5

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

With 0% schema description coverage, the description compensates by listing all four parameters with brief explanations of their purposes (e.g., 'filter asset folders by name', 'ID of the parent folder to filter results'). This adds meaningful semantics beyond the schema's titles, though it lacks format examples or constraints.

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 ('Retrieve a list of asset folders') and resource ('from the current Storyblok space'), distinguishing it from siblings like 'fetch_asset_folder' (singular) and 'fetch_assets' (different resource). It precisely communicates the tool's function without redundancy.

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 does not mention sibling tools like 'fetch_asset_folder' (for single folders) or 'fetch_assets' (for assets rather than folders), nor does it specify prerequisites, exclusions, or contextual usage scenarios.

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