Skip to main content
Glama

Product Images Update

tiendanube_product_images_update
Idempotent

Update a Tiendanube product image's position, alt text, or source URL to correct image details or reorder images in a product listing.

Instructions

Update an image's position, alt text or source. HTTP: PUT /products/{product_id}/images/{id} Required scope: write_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_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesImage ID
altNoAlt text — i18n object keyed by language code, e.g. {"es": "...", "pt": "...", "en": "..."}
srcNoNew source URL
positionNoNew position
product_idYesProduct ID
additional_fieldsNoExtra raw API body fields not covered above; merged into the request body

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false, so the safety profile is largely covered. The description adds auth context (write_products scope) and API versioning, but remains silent on whether omitted fields are preserved or overwritten, and on side effects of replacing 'src'.

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?

One functional sentence followed by the endpoint, scope, and version metadata, with zero filler. The purpose statement is front-loaded, and the operational facts are grouped in a scan-friendly block.

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

Completeness3/5

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

With six parameters including a nested i18n object, no output schema, and annotations that cover safety, the description is minimally viable but leaves open questions about partial-update semantics and the effect of 'additional_fields'. A mutation tool with this much schema surface would benefit from one more sentence on how unspecified fields are treated.

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 including the i18n-shaped 'alt' object and the 'additional_fields' escape hatch is already documented. The description only names three of the six fields at a high level and adds no syntax, format, or interaction detail beyond the schema, so the baseline score 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 ('Update an image's position, alt text or source'), making the mutation target and the editable fields unambiguous. It does not explicitly contrast itself with the adjacent siblings ('product_images_create', 'product_images_upload_unattached'), so an agent must infer differentiation from the name alone.

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?

The 'Required scope: write_products' line is a genuine precondition that helps an agent decide whether it may call this at all. However, there is no explicit guidance on when to choose update versus create/upload, nor any exclusion or prerequisite about the image already existing on the product.

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