Skip to main content
Glama

Product Images Upload Unattached

tiendanube_product_images_upload_unattached

Upload an image to the store repository without attaching it to a product, so it can be linked later.

Instructions

Upload an image to the store repository before attaching it to a product. HTTP: POST /products/images Required scope: write_products API version: 2025-03

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "tiendanube_product_images_upload_unattached"
  }
}

Input Schema

NameRequiredDescriptionDefault
srcNoPublic image URL
filenameNoFile name when using attachment
attachmentNoBase64 image content
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

A4.2/5.0
Behavior4/5

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

Annotations already disclose that this is a non-read-only, non-idempotent, non-destructive, open-world operation. The description adds useful auth context ('Required scope: write_products') and the HTTP endpoint/API version, though it does not describe the response or repository media constraints.

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?

The description is four short lines with the purpose front-loaded, followed by endpoint, required scope, and API version. Every line contributes operational context without repetition.

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 write operation with annotations and full schema coverage, the description supplies enough context to invoke the endpoint correctly. It leaves some workflow gaps, such as what the upload returns or how the unattached image is later attached, and does not clarify that at least one image source field is practically expected.

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 the schema already explains src, filename, attachment, and additional_fields. The description adds no parameter-level meaning beyond the schema, which is the baseline expectation when schema coverage is complete.

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 states a specific verb and resource ('Upload an image to the store repository') and clarifies the scope ('before attaching it to a product'). This distinguishes it from sibling product image tools that attach, update, delete, or list images.

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?

The phrase 'before attaching it to a product' gives clear context for when to use this unattached-upload tool rather than a product-attached image operation. It does not name explicit alternatives or exclusions, so it falls short of full when-to-use guidance.

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