Skip to main content
Glama

update_media

Update a media file's metadata—display name, alt text, or caption—without replacing the file itself.

Instructions

Update metadata for a media file — change the display name, alt text (for accessibility/SEO), or caption. Does not replace the file itself, only its metadata.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "update_media"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesMedia file ID
nameNoNew file name
captionNoImage caption
alternative_textNoAlt text for accessibility

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose one meaningful behavior — that the underlying file is untouched, only metadata changes. However, it omits key mutation semantics: whether unspecified fields are left unchanged or cleared, permission requirements, and idempotency.

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?

Two sentences, front-loaded with the core action, with the scope-limiting clarification immediately following. No filler or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple four-parameter metadata mutation with full schema coverage and no output schema, the description covers what changes and what does not. The remaining gap — partial-update semantics for omitted fields — is a modest but real omission for a write tool without annotations.

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 four parameters are already documented in the schema, making 3 the baseline. The description adds light context (alt text serves accessibility/SEO) but no syntax, format, or partial-update semantics beyond what the schema provides.

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 names a specific verb and resource ("Update metadata for a media file") and enumerates the three mutable fields (display name, alt text, caption). It also implicitly separates itself from upload_media by stating the file itself is not replaced, though it never names that sibling explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: the agent can infer this is for metadata edits, not file replacement, which rules out upload_media. There is no explicit guidance on when to prefer this over update_entry or other siblings, and no stated prerequisites.

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