Skip to main content
Glama

Generate Alt Text

sirv_generate_alt_text
Destructive

Generates AI-written alt text for one image from a public URL or Sirv asset ID; when given an asset ID, it saves the new text to that asset.

Instructions

Write alt text for one image with AI. Give exactly one of image_url or asset_id.

With image_url, the tool returns the text and saves nothing. With asset_id, it writes the text for that library asset and saves it on the asset, in place of its old alt text.

The text follows the workspace's language and brand settings. To save alt text that you wrote yourself, use sirv_update_asset. Returns the alt text.

Credits: spends workspace credits. The cost depends on the model and options.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
orgIdNoWorkspace id from sirv_list_organizations, used with asset_id. Default: the workspace you signed in to
asset_idNoId of a Studio library asset, from sirv_list_assets. The tool saves the text on the asset. Leave it out when you give image_url
image_urlNoPublic URL of an image to describe. The tool returns the text and saves nothing. Leave it out when you give asset_id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.1

TDQS

A4.9/5.0
Behavior5/5

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

Annotations declare destructiveHint=true and openWorldHint=true; the description supplies the specifics those flags only imply: with asset_id the new text replaces the old alt text in place, with image_url nothing is persisted. It also discloses that workspace credits are spent and that cost varies by model and options, which is not derivable from any structured field.

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?

Four short paragraphs, each doing distinct work: what it does, how the two modes differ, where settings come from and which sibling to use instead, and the cost. The mode distinction is front-loaded and there is no filler.

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

Completeness5/5

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

No output schema exists, and the description closes that gap by stating it returns the alt text. Combined with the mutation semantics, credit cost, and the orgId default already documented in the schema, an agent has everything needed to call this correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds a constraint the schema does not encode — the two image sources are mutually exclusive and exactly one is required — which meaningfully guides the call. It does not add format or sizing details beyond that, so it sits just above baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: "Write alt text for one image with AI." It also separates itself from the sibling that does a superficially similar job, sirv_update_asset, which is named as the manual alternative. An agent can identify the tool's function without opening the schema.

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

Usage Guidelines5/5

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

Gives an explicit selection rule — "Give exactly one of `image_url` or `asset_id`" — plus the consequence of each choice, and names sirv_update_asset for the case where the agent already has its own text. Both the when-to-use and the when-to-use-something-else paths are covered.

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