Skip to main content
Glama

Product Images Get

tiendanube_product_images_get
Read-onlyIdempotent

Retrieves a single product image from Tiendanube/Nuvemshop using its product ID and image ID, with optional field selection and JSON or markdown output.

Instructions

Get one product image. HTTP: GET /products/{product_id}/images/{id} Required scope: read_products API version: 2025-03

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": {
      "product_id": "<product_id>",
      "id": "<id>"
    },
    "name": "tiendanube_product_images_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesImage ID
fieldsNoComma-separated list of fields to return, to reduce payload size (e.g. 'id,name,variants')
product_idYesProduct ID
response_formatNoOutput format: 'json' (default, full data) or 'markdown' (human-readable)json

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is fully covered. The description adds genuinely new operational context — the required OAuth scope 'read_products' and the API version 2025-03 — but says nothing about the returned image representation, which matters since no output schema exists.

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 lines, front-loaded with the action, then endpoint, scope and API version. Zero filler; every line carries distinct information.

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?

For a simple single-resource read with full annotation coverage and complete schema descriptions, this is nearly sufficient. The only remaining gap is what fields an image object contains and what 'fields' filtering returns, though the schema example partially covers the latter.

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 four parameters (id, product_id, fields, response_format) are already documented. The HTTP path line reinforces that product_id and id are path identifiers, but adds no syntax or format detail beyond the schema. Baseline 3 applies.

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?

States a specific verb and resource ('Get one product image'), which unambiguously separates it from tiendanube_product_images_list. It stops short of naming the sibling or clarifying the ID-scoping rule, but the singular 'one' does the differentiation work.

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: fetch a single image when you already have both a product_id and an image id. There is no explicit statement of when to prefer this over tiendanube_product_images_list, though the required-scope line gives useful gating context.

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

Deploy Server

Other Tools