Skip to main content
Glama

Describe a photo

update_photo
DestructiveIdempotent

Sets the description (alt text) of a photo, up to 200 characters. The description is the photo's alt text, shown to people who cannot see it, and it appears on the live pages after the site is published again.

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": {
      "site_id": "<site_id>",
      "asset_id": "<asset_id>",
      "alt": "<alt>"
    },
    "name": "update_photo"
  }
}

Input Schema

NameRequiredDescriptionDefault
altYesWhat the photo shows, up to 200 characters.
site_idYesThe site id from list_sites or create_site.
asset_idYesThe photo id (starts with ast_) from list_photos.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, and idempotentHint=true, so the safety profile is known. The description adds genuinely new behavior: the 200-character ceiling and the fact that the change is not live until the site is published again. It stops short of saying the previous alt text is overwritten, which is the main thing that makes this destructive.

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?

Two front-loaded sentences with no padding; the core action and limit come first, then the consequences. Slight redundancy between 'Sets the description' and 'The description is the photo's alt text', but the second sentence earns its place by explaining visibility and publish timing.

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?

With only three fully documented required parameters, no output schema, and rich annotations, the description supplies the missing behavioral context: what the field means, the size limit, and when the change becomes visible. The one gap is not stating that the existing alt text is replaced and whether that is recoverable, which matters given destructiveHint=true.

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%, with alt, site_id, and asset_id all documented in the schema, including the 200-character maxLength and id-prefix hints. The description restates the 200-character limit but adds no syntax or format detail beyond the schema. Baseline 3 applies when the schema carries parameter meaning.

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?

Uses a specific verb ('Sets') with a specific resource and field ('the description (alt text) of a photo'), plus a length bound. This clearly distinguishes it from delete_photo or update_page, though it doesn't name a sibling alternative explicitly. The parenthetical gloss of 'alt text' removes ambiguity about what is being written.

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 context is implied rather than stated: the description notes the alt text is shown to people who cannot see the photo, which signals accessibility motivation. It also states the change appears on live pages only after republishing, which hints at a preview-then-publish workflow. However, there is no explicit when-to-use vs. when-not guidance and no alternative named.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources