Skip to main content
Glama

Get Image

get_image
Read-onlyIdempotent

Read an image from the Brand Library by ID. Returns its status, source, dimensions, description, and workspace, with a link once the image is available.

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_id": "<image_id>"
    },
    "name": "get_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
waitNoHold connection until image reaches terminal status. Only applies to generated images. Recommended: true.
timeoutNoTime to wait for a generated image to finish when waiting is enabled, in seconds. Defaults to and is capped at 45 seconds.
image_idYesImage ID (from generate, upload, or list)
llm_modelNoThe model identifier you are running as, for example "claude-opus-4-8" or "gpt-5.2". Omit it or pass "unknown" if you are not certain; the tool runs the same either way. Recorded only for the server developer's analytics.
include_urlNoIgnored — the URL is always included because this tool has an attached UI widget that needs it to render. Kept in the schema for backward compatibility with existing callers.

Output Schema

NameRequiredDescriptionDefault
idYesImage ID.
widthYesWidth in pixels, or null when not recorded.
heightYesHeight in pixels, or null when not recorded.
promptYesPrompt the image was generated from, or null.
sourceYesgenerated, uploaded, or scraped (collected from a brand source).
statusYesGeneration status, or null when the image has none.
failureYesFailure details of a failed selected-model generation, or null.
image_urlYesLink to the image, or null when a generated image is not completed.
created_atYesTime the image was created.
action_typeYesOperation that produced a generated image, such as generation or edit, or null.
descriptionYesText description of the image, or null when there is none.
aspect_ratioYesClosest standard aspect ratio, or null when unknown.
workspace_idYesWorkspace ID, or null for a personal workspace that has no ID.
failure_reasonYesCoarse reason generation failed, or null. A selected-model generation reports its details in failure on get_image instead.
workspace_nameYesName of the workspace that owns the image.
brand_session_idNoBrand session ID of the image's brand, when included.
variant_group_idYesID of the image's variant group, or null when it has none.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds a meaningful behavioral hint that the image may not be ready yet ('a link once the image is available'), implying an asynchronous status field, but it never explains the wait/timeout polling semantics that dominate correct invocation.

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 tight sentences, front-loaded with the action and resource, followed by the return payload. Nothing is wasted and no sentence repeats the tool name.

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?

An output schema exists, so the description does not need to explain return shapes, and the parameter schema carries the polling details. The only mild redundancy is that the description re-lists the returned fields already present in the output schema, but nothing an agent needs to call it correctly is absent.

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 five parameters (including wait, timeout, and the quirky legacy include_url) are documented in the schema itself; baseline 3 applies. The description adds no parameter-level meaning of its own beyond loosely foreshadowing the availability state.

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 uses a specific verb-plus-resource ('Read an image from the Brand Library by ID') and enumerates the returned fields, which separates it from generate_image, upload_image, and delete_images by implication. It stops short of naming any sibling explicitly, so an agent must infer the boundary rather than read it.

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 only implied: 'by ID' and 'once the image is available' suggest retrieving a known asset that may still be processing. There is no explicit when-to-use versus generate_image/get_generation guidance and no statement about what to do when the ID is unknown or the image fails.

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