Skip to main content
Glama

GotCashback

by com.gotcashback
OverviewDiscussionsAdmin

Set a store alert

set_store_alert
Idempotent

Creates or updates an alert that emails the signed-in user when a store's cashback rate or gift card discount reaches the threshold percent or higher. Use it for 'alert me when Nike cashback hits 10%' or 'tell me when Target gift cards are 15% off'. Re-saving an existing alert updates its threshold and re-arms it. At most 10 active alerts per user. Needs the store_id: take it from an earlier result, or find it with get_stores_by_name (optionally with country_code). Requires OAuth sign-in with a GotCashback account and the 'alerts' scope; anonymous callers are prompted to authorize.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
store_idYesGotCashback's numeric store_id, taken from an earlier result (a store, cashback rate, gift card, deals, favorites or alerts response). If you only have a store name, use the by-name tool instead.
alert_typeYesAlert type: 'cashback' (fires on the store's best flat cash rate: 'up to' rates and airline miles, credit card and points portals are ignored) or 'gift_card' (fires on the store's best gift card discount). Use the alert_type value from get_my_alerts as-is.
threshold_percentYesFire when the rate/discount reaches this percent or higher (greater than 0, at most 100), e.g. 10 for 10%

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / alert_type / description
      Previous value: -"Alert type: 'cashback' (fires on the store's best cashback rate) or 'gift_card' (fires on the store's best gift card discount). Use the alert_type value from get_my_alerts as-is."New value: +"Alert type: 'cashback' (fires on the store's best flat cash rate: 'up to' rates and airline miles, credit card and points portals are ignored) or 'gift_card' (fires on the store's best gift card discount). Use the alert_type value from get_my_alerts as-is."
  2. Changed2 schema fields changed
    • changedInput schema / properties / alert_type / description
      Previous value: -"Alert type: 'cashback' (fires on the store's best cashback rate) or 'gift_card' (fires on the store's best gift card discount)"New value: +"Alert type: 'cashback' (fires on the store's best cashback rate) or 'gift_card' (fires on the store's best gift card discount). Use the alert_type value from get_my_alerts as-is."
    • addedInput schema / properties / alert_type / enum
      Added value: +[
+  "gift_card",
+  "cashback"
+]
  3. First observed

TDQS

A4.9/5.0
Behavior5/5

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

The description adds substantial behavior beyond annotations: re-saving updates the existing alert's threshold and re-arms it, there is a 10-active-alert cap, it emails the signed-in user, and requires OAuth with the 'alerts' scope. It also clarifies that anonymous callers are prompted to authorize. This is consistent with idempotentHint=true and destructiveHint=false.

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 purpose, then examples, then behavioral constraints and prerequisites. Every sentence adds distinct information: purpose, use cases, update semantics, limit, store_id sourcing, and auth requirements. There is no filler or redundancy.

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 mutation tool with no output schema, the description covers all essential calling context: what it does, how to identify the store, how re-saving behaves, the active-alert limit, and authentication requirements. An agent has enough information to decide when to invoke it and how to populate the required parameters correctly.

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

Parameters4/5

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

The schema already fully describes all three parameter fields, so the baseline is 3. The description adds value by giving real-world threshold examples, explaining that re-saving updates the threshold, and providing practical store_id sourcing workflow. It does not merely repeat 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?

The description states a specific verb and resource: 'Creates or updates an alert that emails the signed-in user when a store's cashback rate or gift card discount reaches the threshold percent or higher.' It also gives concrete example intents, and its semantics are clearly distinct from sibling tools like get_my_alerts and remove_store_alert.

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?

It gives explicit usage examples, indicates where to source store_id ('take it from an earlier result, or find it with get_stores_by_name'), and states auth prerequisites. The guidance to use the by-name tool when only a name is available is a clear when-to-use/when-not-to-use distinction.

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

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