Skip to main content
Glama

fetch_assets

Retrieve multiple assets from Storyblok with filters such as search, folder, tags, and sort order. Paginate results and filter by private status, alt text, title, or copyright.

Instructions

Retrieve multiple assets from Storyblok Management API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number
per_pageNoItems per page
searchNoSearch query for filtering assets
folder_idNoFilter by folder ID
sort_byNoSort order for assets
is_privateNoFilter by private status
by_altNoFilter by alt text
by_titleNoFilter by title
by_copyrightNoFilter by copyright
with_tagsNoFilter by tags
Behavior2/5

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

With no annotations, the description carries full burden for behavioral disclosure. It only states 'retrieve' without noting pagination, rate limits, authentication, or response behavior. Minimal value added beyond the schema.

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?

Single sentence, direct and efficient. No wasted words, but could be slightly more informative without harming conciseness.

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?

Complete for a simple retrieval tool with well-defined schema, but lacks explanation of return format, error handling, or pagination behavior that would help an agent.

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% with adequate parameter descriptions. The description adds no extra meaning or context to parameters, but the schema itself is sufficient.

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 it retrieves multiple assets from a specific API (Storyblok Management API). However, it does not differentiate from sibling tools like 'get_asset' (singular) or other list tools, missing a chance to clarify scope.

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 (e.g., get_asset for single, bulk operations). The description provides no context for appropriate use cases.

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