SiteCheck Shop & Social

MediaMarkt / MediaWorld product search for Germany

ecommerce_mediamarkt_eu

Read-only

MediaMarkt / MediaWorld product search for Germany, Austria, Switzerland, Italy (MediaWorld) and Poland, read from the schema.org product list on the public search page: product name, price and currency (EUR, CHF or PLN), average rating, review count, image and product URL for the top 12 results, plus the total number of matching products. A search that matches a category or brand returns that page's top products. Related tools on this server, for a different need: ecommerce_eu_safety_gate_rapex when you need EU Safety Gate weekly product-safety report index. Price: $0.002 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

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": {
      "q": "<q>"
    },
    "name": "ecommerce_mediamarkt_eu"
  }
}

Input Schema

Name	Required	Description	Default
`q`	Yes	Search words in the shop's language, e.g. kaffeemaschine, laptop (required, 2-80 chars)
`country`	No	de (default), at, ch, it or pl

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Goes well beyond the supplied readOnlyHint/openWorldHint: it names the data source (schema.org product list on the public search page), the result cap (top 12), that a total-match count is included, the accepted currencies, and the paid-call model ($0.002 USDC via x402 on Base/Solana/Arc with failed calls free). Those are exactly the cost and side-effect facts an agent needs before calling a metered tool.

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-loads purpose, scope and returned fields, then tacks on the sibling pointer and pricing at the end, so an agent can stop reading early. The final two sentences are dense and mix unrelated concerns (alternative tool, payment rails), which costs a point on structure rather than length.

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

Completeness5/5

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

A two-parameter read tool with an output schema, so return shape needn't be explained; the description still covers source, result cap, currency set, pricing and the category/brand query edge case. Nothing material is missing for correct invocation.

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 coverage is 100%, so the baseline is 3, but the description adds meaning the schema lacks: it maps country values to their storefronts (Italy = MediaWorld) and notes that the shop's own language should be used for queries. Minor gap: it does not mention the 2-80 character constraint that lives in the schema.

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?

States a specific verb and resource ('product search') and pins down the exact retailer and five-country scope (de/at/ch/it/pl, MediaWorld for Italy). It also enumerates the returned fields (name, price and currency, rating, review count, image, URL, total matches), so an agent can distinguish it from generic marketplace siblings 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?

Explicitly routes one adjacent need away ('ecommerce_eu_safety_gate_rapex when you need EU Safety Gate weekly product-safety report index') and clarifies that category or brand queries return that page's top products rather than an error. It does not, however, tell the agent when to prefer this over the many other regional shop tools (aliexpress, trendyol, hepsiburada) beyond the country list.

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

All SiteCheck Shop & Social tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?