Skip to main content
Glama

Get one image

get_image
Read-only

Everything known about a single listing: its description, keywords, price in credits and money, the license it sells under, and a preview. Use after search_images when the person wants a closer look at one option.

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": {
      "listing_id": "<listing_id>"
    },
    "name": "get_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
listing_idYes

Output Schema

NameRequiredDescriptionDefault
matchNo
ownedNo
priceYes
titleYes
pixelsYes
licenceYes
headlineYes
keywordsYes
shape_fitNo
collectionYes
listing_idYes
descriptionYes
orientationYes
preview_urlYes
aspect_ratioYes
photographerYes
owned_licencesNo
licence_summaryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered without description support. The description's remaining content enumerates return fields, which is largely redundant given an output schema exists. It adds no context on auth, error behavior when a listing_id is invalid, or what 'preview' actually contains.

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, zero filler. The payload (what you get back) is front-loaded and the usage routing follows immediately.

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?

A one-parameter read tool with an output schema and read-only annotations needs little explanation, and the description covers purpose and sequencing. The only material gap is that the caller is never told what listing_id identifies or where to obtain it.

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

Parameters2/5

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

Schema description coverage is 0% for listing_id, and the description never mentions the parameter or where its value comes from. The phrase 'after search_images' lightly implies the ID originates from search results, but the required identifier itself is never explained or format-qualified.

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 description names the specific resource (a single listing) and enumerates exactly what is returned — description, keywords, price in credits and money, license, preview — which lets an agent separate it from search_images at a glance. No ambiguity about singular vs. list scope.

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

Usage Guidelines4/5

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

It explicitly names the predecessor step and condition: 'Use after search_images when the person wants a closer look at one option.' That routes the agent correctly between the two tools. It stops short of stating when-not to use it (e.g., for bulk retrieval or when only a thumbnail is needed).

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