GotCashback

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 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.
`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. Dates show when Glama detected each change.

First observedSep 6, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already mark the tool as read-only, idempotent, and non-destructive, and the description adds meaningful behavior beyond that: multiple matching stores are returned best-match-first with one entry per country, an empty gift_cards list means no current discounts, and the returned url is a tracked purchase link. This gives the agent important runtime behavior without contradicting any annotation.

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 description is front-loaded with the core purpose, then flows naturally into usage examples, output behavior, alternative tools, and user-presentation instructions. Every sentence carries actionable information with no redundant filler or restatement of the title.

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?

For a tool with two parameters, one required, the description is complete: it explains what triggers this tool, how results are ordered and structured, what an empty list means, which sibling to use instead, and exactly how the agent should present results to the user. The presence of an output schema means the return-shape details are already covered elsewhere.

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 fully documents store_name and country_code including matching semantics, examples, and ISO format notes. The main description adds no substantial parameter-level meaning beyond reinforcing that the lookup is by store name, so the baseline score of 3 is appropriate.

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 states a specific verb ('Finds a store by name'), the resource ('discounted gift cards'), and the exact output fields (face value, price, discount percent, digital or physical). It explicitly differentiates from the sibling get_gift_cards_by_store_id and get_cashback_rates_by_store_name, so an agent can identify this tool immediately.

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 gives explicit when-to-use guidance: 'preferred first call for any gift card question that names a store', includes concrete example queries, and states 'No prior lookup is needed.' It also names the precise alternatives: use get_gift_cards_by_store_id when a store_id is already known, and get_cashback_rates_by_store_name for cashback questions.

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

All GotCashback tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0

Disambiguation4/5

Most tools target a clearly distinct resource and action, and the descriptions carefully cross-reference when to use each one. The main risk is the similar get_stores_by_name, get_cashback_rates_by_store_name, and get_gift_cards_by_store_name names, though their descriptions do a good job of separating identity, cashback rates, and gift cards.

Naming Consistency4/5

The naming follows a mostly consistent get_<resource>_by_<selector> pattern with clear verb prefixes for mutations like set, remove, and toggle. Minor inconsistencies exist, such as get_portal_by_id (singular) versus get_portals_by_name (plural), and the get_my_* cluster for account tools.

Tool Count4/5

Eighteen tools is slightly above the ideal 3-15 range, but the count is justified by the breadth of the domain: store comparison, brand and category deals, gift cards, portals, countries, and user account features. Each tool has a distinct purpose, so the set does not feel genuinely bloated.

Completeness4/5

The tool surface covers the main workflows well: finding cashback by store, brand, or category, comparing gift cards and portls, browsing countries and stores, and managing favorites, alrts, and profile. Minor gaps exist, such as no direct way to rank all stores in a country by cashback rate without per-store lookups, but agents can work around these.

Resources

Need Help?