Skip to main content
Glama
MediaMarkt & Saturn MCP
by washedguy

search_products

Search MediaMarkt, MediaWorld, or Saturn storefronts by product keywords, model number, or EAN to find product names, prices, and home delivery options.

Instructions

Search the selected MediaMarkt, MediaWorld or Saturn storefront for product names, prices and home delivery. Search can return suggestions unrelated to the query; verify relevance. Redirected landing pages return only visible products with available data, may include unrelated products, and support local brand/price filters on visible products only, but not delivery filters or pagination. Set include_offers to inspect linked variants and embedded marketplace offers for each result; slower and not exhaustive. Use get_product for exact IDs or URLs. Returns pagination for more results.

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": {
      "query": "<query>"
    },
    "name": "search_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoResults page, starting at 1. Use next_page to continue.
brandNoExact retailer brand name, e.g. SONY.
freshNoBypass the process cache and request current shop data.
queryYesProduct keywords, model number, or EAN. Local-language terms may work best.
countryNoStorefront country code. Defaults to de. Product and store IDs are country-specific.de
languageNoShop language; defaults to the country's main language. Switzerland: de/fr/it; Belgium: nl/fr.
retailerNoStorefront brand: mediamarkt (including MediaWorld in Italy) or saturn (Germany only).mediamarkt
max_priceNoMaximum price in the local currency.
min_priceNoMinimum price in the local currency.
delivery_onlyNoUse the storefront in-stock delivery filter (not store pickup); unsupported for Spain, Italy and Türkiye.
include_offersNoFetch each product page to include linked variants and embedded marketplace offers. Slower; results are not exhaustive.

Output Schema

NameRequiredDescriptionDefault
noteNo
pageYes
cacheNo
countYes
queryYes
pagingYes
sourceYes
countryNode
coverageYes
languageNode
productsYes
retailerYes
next_pageYes
observed_atNo
local_filtersNo
redirected_urlNo
total_productsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.0

TDQS

A4.5/5.0
Behavior5/5

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

With no annotations, the description carries the full behavioral burden and discloses non-obvious traits: search can return unrelated suggestions, redirected landing pages expose only visible products with available data, local brand/price filters work only on visible products, and delivery filters or pagination are unsupported there. It also warns that include_offers is slower and not exhaustive.

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?

The description is dense but front-loaded, leading with the core action and following with caveats and alternatives. The redirected-landing-page sentence is somewhat run-on and jargon-heavy, but every sentence carries relevant operational 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 an 11-parameter tool with an output schema, the description covers the most important quirks and the get_product alternative. It leaves the term 'redirected landing pages' somewhat opaque and does not discuss permissions or auth, but the return structure is covered by the output schema.

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

Parameters4/5

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

Schema description coverage is 100%, so the baseline is 3. The description adds operational meaning beyond the schema for include_offers (slower, not exhaustive) and clarifies that brand/price filtering applies only to visible products on redirected pages while delivery filtering and pagination do not.

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: search product names, prices, and home delivery across MediaMarkt, MediaWorld, or Saturn storefronts. It also explicitly distinguishes this from get_product for exact IDs or URLs, so an agent can identify the tool's role without opening the schema.

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 gives clear usage guidance: use get_product for exact IDs or URLs, set include_offers to inspect variants and marketplace offers, and verify relevance because results may be unrelated suggestions. It does not broadly frame when exploratory search should be preferred over other discovery approaches, but the main alternative is named.

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