GotCashback MCP

Gift card discounts by store name

get_gift_cards_by_store_name

Read-onlyIdempotent

Finds a store by name and returns the discounted gift cards currently on sale for it from multiple gift card sellers — face value, price, discount percent, digital or physical — so the user can compare every seller and see the best discount. This is the preferred first call for any gift card question that names a store: 'best gift card discount for Gap', 'where can I buy discounted Instacart gift cards', 'compare Home Depot gift card discounts', 'current Target gift card deals'. No prior lookup is needed. Returns every matching store (best match first, one entry per country), each with its 'gift_cards' list and a 'gift_cards_url' page; an empty 'gift_cards' list means no discounted cards right now. Use get_gift_cards_by_store_id only when a store_id is already known, and get_cashback_rates_by_store_name when the user asks about cashback rates instead. Present every returned seller's listing to the user (a table with a link column, not only the best discount) and always show each gift card's 'url' as a clickable link — that tracked link is where the user buys the card at the discounted price. Also mention the store's 'gift_cards_url' page.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`store_name`	Yes	The retailer or brand name as a shopper would say it, e.g. 'Walmart', 'Nike', 'Best Buy', 'Expedia', 'Home Depot'. Matched case-insensitively at word boundaries of the store name and its known alternate names (exact name, then names starting with it, then names containing it as a word), best match first; a partial-word match (e.g. 'gap' inside 'Singapore') is only returned when nothing better exists. Pass the plain name only — no words like 'cashback', 'gift card' or a country.
`country_code`	No	Optional. Lowercase ISO 3166-1 alpha-2 country code that limits results to one country, e.g. 'us' (United States), 'ca' (Canada), 'gb' (United Kingdom — use 'gb', not 'uk'), 'de' (Germany), 'au' (Australia), 'fr' (France). Pass it when the user names a country ('in Canada', 'UK cashback'); omit it to search all supported countries.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`stores`	No	Matching stores (one entry per country). Empty when nothing matched.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 7, 2026

changedInput schema / properties / store_name / description

Previous value: -"The retailer or brand name as a shopper would say it, e.g. 'Walmart', 'Nike', 'Best Buy', 'Expedia', 'Home Depot'. Matched as a case-insensitive substring of the store name and its known alternate names, best match first. Pass the plain name only — no words like 'cashback', 'gift card' or a country."New value: +"The retailer or brand name as a shopper would say it, e.g. 'Walmart', 'Nike', 'Best Buy', 'Expedia', 'Home Depot'. Matched case-insensitively at word boundaries of the store name and its known alternate names (exact name, then names starting with it, then names containing it as a word), best match first; a partial-word match (e.g. 'gap' inside 'Singapore') is only returned when nothing better exists. Pass the plain name only — no words like 'cashback', 'gift card' or a country."

First observedSep 4, 2026

TDQS

A5/5.0

Behavior5/5

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

The annotations already declare readOnlyHint and idempotentHint, but the description adds substantial behavioral details: the store-name matching algorithm (case-insensitive, word boundaries, best-match-first), the structure of results (gift_cards list, gift_cards_url), and that an empty list means no discounted cards. This exceeds what annotations provide and discloses the tool's behavior transparently, with no contradictions.

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?

Though the description is long, every sentence serves a purpose: it covers functionality, usage alternatives, matching rules, output details, presentation instructions, and edge cases. There is no redundancy or filler; the structure is dense but well-organized, making it appropriately sized for the complexity of the tool.

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?

The description is complete for the tool's context. It explains the output format and how to use it (clickable link, mention gift_cards_url), handles empty results, and clarifies the distinction from related tools. Even with an output schema present, the description provides necessary context that the schema alone does not convey.

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

Parameters5/5

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

Both parameters have detailed descriptions in the schema. store_name includes matching rules and example values, and country_code specifies format, allowed values, and when to use it. The schema description coverage is 100% and the tool description reinforces parameter handling, making parameter semantics fully explicit.

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 clearly states the tool's function: finding a store by name and returning discounted gift cards from multiple sellers. It also distinguishes it from sibling tools like get_cashback_rates_by_store_name and get_gift_cards_by_store_id, making the purpose unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly states when to use this tool ('preferred first call for any gift card question that names a store'), when not to (use get_gift_cards_by_store_id when store_id is known), and that no prior lookup is needed. It also provides guidance on presenting results, fulfilling the usage guideline requirement thoroughly.

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

All GotCashback 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?