Skip to main content
Glama

Translate Image Text

sirv_translate_image_text

Translate visible text in an image into another language while preserving layout and style. Use for packaging, banners, and infographics; returns a translated image URL.

Instructions

Translate the visible text in one image into another language. The layout, type style and the rest of the image stay the same.

Use it for packaging, banners and infographics. Do not use it for plain text that is not in an image: translate that yourself. For other changes to the image, use sirv_edit_image.

Inputs: image_url and target_language (a code or a name, such as es or Spanish) are required. source_language is optional. model defaults to nano-banana-lite-edit.

The source image does not change. Returns result_url, the translated image.

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

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": {
      "image_url": "<image_url>",
      "target_language": "<target_language>"
    },
    "name": "sirv_translate_image_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelNoTranslation model. Default: nano-banana-lite-editnano-banana-lite-edit
image_urlYesPublic URL of the image whose text to translate
source_languageNoLanguage of the text in the image now, as a code or a name. Optional
target_languageYesLanguage to translate into, as a code or a name, such as es or Spanish

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.1

TDQS

A4.4/5.0
Behavior4/5

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

Goes beyond the annotations by disclosing that the source image is not modified, that the call spends workspace credits with cost varying by model, and what the return value looks like (result_url). Annotations already cover the safety profile (destructiveHint=false, openWorldHint=true), so the remaining gap is minor — no note on latency or that repeated calls are non-idempotent despite the idempotentHint=false flag.

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?

Front-loaded with the core purpose and the key exclusion, then a compact inputs/outputs/cost block. The 'Inputs:' section is somewhat redundant against a 100%-covered schema, which keeps it out of 5 territory, but no sentence is wasted.

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?

For a 4-parameter image-generation tool with no output schema, the description covers purpose, exclusions, required vs optional inputs, the default model, side effects on the source asset, the return value, and the credit cost. An agent has everything needed to call it correctly.

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 every parameter is already documented in structured data, and the description largely restates it (required image_url/target_language, optional source_language, model default). The added value is the example clarification that target_language accepts a code or a name, but this is already present in the schema.

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?

The first sentence names a specific verb and resource — 'Translate the visible text in one image into another language' — and immediately scopes what is preserved ('layout, type style and the rest of the image stay the same'). This is clearly distinguishable from sirv_edit_image and from plain-text translation.

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?

Explicit positive cases (packaging, banners, infographics), an explicit exclusion ('Do not use it for plain text that is not in an image: translate that yourself'), and an explicit redirect to the sibling for other image changes. Both when-to-use and when-not-to-use are stated.

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