Skip to main content
Glama

create_media

Register a media item in Agentic CMS by providing its filename and URL, with optional metadata like dimensions, caption, alt text, and MIME type.

Instructions

Register a media item in the CMS.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesURL where the media is accessible
widthNoWidth in pixels
heightNoHeight in pixels
captionNoCaption for the media
alt_textNoAlt text for accessibility
filenameYesFilename of the media
file_sizeNoFile size in bytes
mime_typeNoMIME type (e.g., image/png)
created_byNoWho uploaded this media
storage_pathNoStorage path (e.g., S3 key)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, the description must disclose behavioral traits, but it only implies a write operation. It omits permissions, side effects, idempotency, duplicate handling, and other mutation characteristics.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The single sentence is front-loaded and free of waste, but it is too sparse to adequately convey the tool's scope, making it under-specified rather than genuinely concise.

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?

For a mutation tool with 10 parameters, no annotations, and no output schema, the description is too minimal. It lacks behavioral details and usage context needed for correct invocation.

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 description coverage is 100%, so all 10 parameters are documented in the schema. The description adds no additional meaning beyond the schema, making a baseline 3 appropriate.

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 states a specific verb ('Register') and resource ('media item') within the CMS, making the tool's purpose clear. However, it does not explicitly differentiate from sibling tools like list_media or probe_media, though no direct creation sibling exists.

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 when-to-use guidance, prerequisites, or alternatives are provided. The description only restates the action, leaving the agent to infer context from the name and schema.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.