ZoZoPeak: Verified Coupons & Deals MCP

Find Coupon Codes

find_coupons

Read-onlyIdempotent

Looks up coupon codes for one online store. Offers come from official affiliate-network feeds; each offer shows when it was last seen in its feed (null when the feed does not report it); offers past their listed end date are never returned. Badges mark TakeDeals-verified coupons and official brand-program coupons. Results are ranked verified first, then by stated saving, never by commission. Links may be affiliate links at no cost to the shopper. Use when the user asks for a promo, coupon or discount code for a named store. An empty list means no code is listed right now.

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": {
      "store": "<store>"
    },
    "name": "find_coupons"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Results to return, 1 to 10, default 5.
`store`	Yes	Store name, domain or any URL on the store, for example 'aliexpress.com'. Any spelling that names the store is matched to it.
`country`	No	Shopper's two-letter ISO country code such as US, GB or AE. Keeps offers valid for that country, including worldwide ones.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A4.1/5.0

Behavior5/5

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

The annotations already declare a safe, idempotent, closed-world read, and the description still adds substantial behavior: data provenance (official affiliate-network feeds), last-seen semantics including the null case, exclusion of past-end-date offers, badge meanings, and an explicit ranking rule ('verified first, then by stated saving, never by commission'). It also discloses the affiliate-link monetization, which an agent might otherwise not surface to a user.

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 the purpose, then stacks behavior, then closes with the usage trigger and empty-result meaning — well ordered with no filler sentences. It is dense and long for a single block, and the usage trigger would read better near the front, but no sentence is wasted.

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?

There is no output schema, and the description fills that gap by explaining result provenance, timestamp/null semantics, badge fields, ranking order and the empty-list meaning. Nothing an agent needs in order to call this correctly or explain results to a user is missing.

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 store, country and limit parameters are already fully documented, and the description adds almost nothing param-specific beyond reinforcing the single-store scoping. Baseline 3 is appropriate when the schema carries the parameter burden.

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?

Opens with a specific verb and resource — 'Looks up coupon codes for one online store' — which cleanly separates it from the sibling find_store_deals, since this tool is scoped to a single named store. It never names that sibling outright, so the differentiation is inferred from the resource noun rather than stated.

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 an explicit trigger — 'Use when the user asks for a promo, coupon or discount code for a named store' — plus an interpretation rule for the empty case ('no code is listed right now'). It does not name find_store_deals or state when to prefer it, so the when-not guidance is absent.

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

All ZoZoPeak: Verified Coupons & Deals MCP 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?