Skip to main content
Glama

update_asset

Update an existing asset's metadata and configuration: folder, tags, lock, privacy, scheduling, focus, alt, title, source, copyright, and custom fields.

Instructions

Update an existing asset's metadata or settings.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
asset_idYesID of the asset to update
asset_folder_idNoNew folder ID for the asset
internal_tag_idsNoList of internal tag IDs
lockedNoLock status of the asset
is_privateNoPrivate status of the asset
publish_atNoISO datetime for scheduled publish
expire_atNoISO datetime for scheduled expiration
focusNoFocus point for image cropping
altNoAlt text for the asset
titleNoTitle of the asset
sourceNoSource information
copyrightNoCopyright information
meta_dataNoAdditional metadata
Behavior2/5

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

No annotations are provided, and the description only says 'Update an existing asset's metadata or settings.' It does not disclose permissions, idempotency, partial update behavior, 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.

Conciseness4/5

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

The description is a single sentence with no wasted words. It is concise, though it could benefit from slightly more detail.

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?

Given the tool has 13 parameters including a nested object and no output schema, the description is too minimal. It lacks details on return values, partial updates, and behavior for optional 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?

Input schema has 100% description coverage, so the schema already explains parameters well. The description adds no extra meaning beyond the schema, which is acceptable.

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?

Description clearly states the tool updates an asset's metadata or settings. It uses a specific verb and resource, but does not differentiate itself from sibling update tools like update_asset_folder or update_story.

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. The description does not mention prerequisites, when not to use it, or compare with related tools.

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