Skip to main content
Glama

Zalando Product

run_zalando_products
Read-onlyIdempotent

Get full Zalando product details by product URL: name, brand, colour, price, list price, discount, 30-day lowest price, images, description, category, stock, sizes with stock levels, attributes (material, care, details) and colour variants. Flat 5 points per successful run.

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": "<product>"
    },
    "name": "run_zalando_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
productYesProduct page URL. e.g. https://www.zalando.de/nike-sportswear-court-borough-recraft-unisex-sneaker-low-white-ni116d0lr-a15.html

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive behavior, so the safety profile is covered. The description adds genuinely new behavior: the flat 5-point cost per successful run, which tells the agent the billing model and that failures are not charged. It does not mention auth or rate limits, but the cost disclosure is a meaningful addition.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core action, followed by a compact field enumeration and the cost note. The field list is long but each item conveys real payload content for a tool with no output schema, so it earns its place; a slightly tighter grouping would be ideal.

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?

With no output schema, the description compensates by enumerating the returned fields (price, list price, 30-day lowest price, stock, sizes, variants, attributes), which is exactly what an agent needs to judge fitness. It is nearly complete, missing only usage routing to the search/related siblings.

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% and the single parameter (product) is already fully documented with an example URL in the schema. The description only restates 'by product URL' with no added syntax or edge-case detail, so the 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?

Specific verb (Get) plus resource (full Zalando product details) and the input mode (by product URL), with an enumerated field list that makes the return scope concrete. It does not name the sibling tools it must be distinguished from (run_zalando_products_search, run_zalando_products_related), but the URL-based single-product scope is unambiguous.

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 implied: you supply a product URL to fetch that product's details, which naturally contrasts with the search and related siblings. However, there is no explicit when-to-use or when-not-to-use guidance, and no statement of what the URL must look like or what happens on an invalid URL.

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