Bestshopping Cashback — IT, DE, FR

get_merchant

Read-onlyIdempotent

Read public information, conditions and browser tracking rules for an eligible Bestshopping retail merchant in the selected account market. Excluded merchants are unavailable even by ID. Exact rates are on the returned Bestshopping page; no personalized quote or private account access. Cashback is reserved for eligible account holders aged 18 or over.

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": {
      "merchant_id": "<merchant_id>",
      "market": "<market>"
    },
    "name": "get_merchant"
  }
}

Input Schema

Name	Required	Description	Default
`market`	Yes	Bestshopping ACCOUNT market: it (Italy), de (Germany), fr (France). Ask the user if missing or ambiguous; never infer it from language or reuse IDs across markets.
`merchant_id`	Yes	Merchant ID returned by search_merchants. Never guess or reuse IDs from another market.

Output Schema

Name	Required	Description	Default
`merchant`	Yes
`conditions`	Yes
`description`	Yes
`rate_notice`	Yes
`cashback_rate`	Yes
`tracking_rules`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 22, 2026

removedOutput schema / properties / checked_at

Removed value: -{
-  "format": "date-time",
-  "type": "string"
-}

changedOutput schema / required

Previous value: -[
-  "merchant",
-  "description",
-  "conditions",
-  "cashback_rate",
-  "rate_notice",
-  "tracking_rules",
-  "checked_at"
-]New value: +[
+  "merchant",
+  "description",
+  "conditions",
+  "cashback_rate",
+  "rate_notice",
+  "tracking_rules"
+]

Changed4 schema fields changedOct 21, 2026

removedInput schema / properties / market / default
```
Removed value: -"it"
```

changedInput schema / properties / market / enum

Previous value: -[
-  "it"
-]New value: +[
+  "it",
+  "de",
+  "fr"
+]

changedInput schema / required

Previous value: -[
-  "merchant_id"
-]New value: +[
+  "merchant_id",
+  "market"
+]

changedOutput schema / properties / merchant / properties / market / enum

Previous value: -[
-  "it"
-]New value: +[
+  "it",
+  "de",
+  "fr"
+]

Changed3 schema fields changedOct 21, 2026

changedInput schema / properties / market / description

Previous value: -"Bestshopping market. Only Italy is enabled."New value: +"Bestshopping ACCOUNT market: it (Italy), de (Germany), fr (France). Ask the user if missing or ambiguous; never infer it from language or reuse IDs across markets."

removedOutput schema / properties / merchant / properties / market / const
```
Removed value: -"it"
```
addedOutput schema / properties / merchant / properties / market / enum
```
Added value: +[
+  "it"
+]
```

First observedOct 21, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, closed-world, so the bar is lower; the description still adds real context: excluded merchants fail even with a valid ID, no personalized quote or private account access, and cashback is limited to eligible holders aged 18+. That materially shapes expectations about failure cases and the nature of returned data.

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?

Four short sentences, front-loaded with the action and scope, then eligibility caveats. No filler sentences, though the eligibility/age line sits slightly apart from the core read operation.

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?

Output schema exists, so return-value detail is not required. The description covers the eligibility gate, market scoping, and the exclusion failure mode, which is everything an agent needs before invoking a two-parameter read.

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 coverage is 100% and both parameters already carry rich descriptions including the market enum and 'never guess or reuse IDs'. The description only reinforces market scoping ('in the selected account market') and the excluded-merchant constraint; it adds little beyond the schema, which is the expected baseline.

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?

A specific verb ('Read') plus a scoped resource: public info, conditions and browser tracking rules for one merchant in the selected market. It is clearly distinguishable from search_merchants (single-ID lookup rather than discovery), though it never names that sibling.

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 by 'Excluded merchants are unavailable even by ID' and the note that exact rates live on the returned page, so the agent infers this is the detail-fetch step after search. But no sibling is named and there is no explicit when-to-use / when-to-prefer-alternative routing (e.g. search_merchants to find an ID, prepare_cashback_link for the actual cashback action).

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

All Bestshopping Cashback — IT, DE, FR 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?