Bestshopping Cashback — IT, DE, FR

prepare_cashback_link

Read-onlyIdempotent

Prepare a personal Bestshopping go.html link for an eligible account holder aged 18 or over, using their exact nickname and an eligible retail merchant in the selected market. If the user says they are under 18, explain the age requirement and do not prepare a link. Does NOT authenticate age or identity, activate cashback, follow the URL, set merchant cookies, register a purchase click or make a purchase. Show the link and tell the USER to click it in their shopping browser, allow tracking cookies and disable AdBlock. Never open or prefetch the link or claim cashback is already activated.

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>",
      "nickname": "<nickname>",
      "market": "<market>"
    },
    "name": "prepare_cashback_link"
  }
}

Input Schema

Name	Required	Description
`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.
`nickname`	Yes	Exact nickname for the selected Bestshopping market explicitly supplied by the user. Ask if missing. Never request a password.
`merchant_id`	Yes	Merchant ID returned by search_merchants. Never guess or reuse IDs from another market.

Output Schema

Name	Required	Description	Default
`status`	Yes
`message`	Yes
`merchant`	Yes
`conditions`	Yes
`activation_url`	Yes
`tracking_rules`	Yes
`tracking_activated`	Yes
`user_click_required`	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: -[
-  "status",
-  "tracking_activated",
-  "user_click_required",
-  "activation_url",
-  "merchant",
-  "conditions",
-  "tracking_rules",
-  "message",
-  "checked_at"
-]New value: +[
+  "status",
+  "tracking_activated",
+  "user_click_required",
+  "activation_url",
+  "merchant",
+  "conditions",
+  "tracking_rules",
+  "message"
+]

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",
-  "nickname"
-]New value: +[
+  "merchant_id",
+  "nickname",
+  "market"
+]

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

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

Changed4 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."

changedInput schema / properties / nickname / description

Previous value: -"Exact Bestshopping Italy nickname explicitly supplied by the user. Ask if missing. Never request a password."New value: +"Exact nickname for the selected Bestshopping market explicitly supplied by the user. Ask if missing. Never request a password."

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

A4.5/5.0

Behavior5/5

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

Annotations already mark it read-only, non-destructive, idempotent, and closed-world, but the description adds substantial operational boundaries: it does not authenticate age/identity, activate cashback, follow the URL, set cookies, register clicks, or make purchases. It also instructs showing the link to the user, telling them to click it with tracking cookies allowed and AdBlock disabled, and never prefetching or claiming activation.

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 purpose is front-loaded, and every sentence earns its place by covering the age gate, prohibited actions, and required user instructions. Despite being longer than average, the length is justified by the safety-critical behavior.

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?

With an output schema and rich annotations already present, the description still covers eligibility, input expectations, post-call user handling, and prohibited actions. Nothing critical is missing for an agent to call this correctly.

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 market, nickname, and merchant_id in detail. The description reinforces exact nickname and eligible merchant in the selected market, but adds little syntax or parameter-level detail beyond 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: prepare a personal Bestshopping go.html link. It adds the key scope conditions (eligible account holder aged 18+, exact nickname, eligible merchant, selected market), making it distinct from the sibling merchant lookup tools.

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?

Gives clear when-to-use and when-not-to-use guidance, including handling under-18 users by explaining the age requirement and not preparing a link. It also specifies post-generation behavior, but does not explicitly name search_merchants or other alternatives for obtaining merchant_id.

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?