GotCashback

My alerts

get_my_alerts

Read-onlyIdempotent

Returns the signed-in user's cashback and gift card alerts. Use it for 'what alerts do I have?' or before changing an alert. Each alert carries store_id, alert_type ('cashback' or 'gift_card'), threshold_percent and the last notification; pass store_id and alert_type straight to set_store_alert or remove_store_alert — the values are identical. Requires OAuth sign-in with a GotCashback account and the 'alerts' scope; anonymous callers are prompted to authorize.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`alerts`	No	The user's alerts, newest first. Empty when they have none.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed1 schema field changedSep 6, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "The signed-in user's store alerts.",
+  "properties": {
+    "alerts": {
+      "description": "The user's alerts, newest first. Empty when they have none.",
+      "items": {
+        "description": "An alert the user has set on a store: it notifies them by email when the store's cashback rate or gift card discount reaches the threshold.",
+        "properties": {
+          "active": {
+            "description": "True while the alert is armed. Inactive alerts no longer notify and do not count against the 10-alert limit.",
+            "type": "boolean"
+          },
+          "alert_id": {
+            "description": "GotCashback's numeric identifier for this alert subscription. Informational — remove_store_alert takes store_id and alert_type, not this id.",
+            "type": "integer"
+          },
+          "alert_type": {
+            "description": "What the alert watches: 'cashback' (the store's best cashback rate) or 'gift_card' (the store's best gift card discount). Pass this value unchanged to set_store_alert or remove_store_alert.",
+            "enum": [
+              "gift_card",
+              "cashback"
+            ],
+            "type": "string"
+          },
+          "country_code": {
+            "description": "Lowercase ISO 3166-1 alpha-2 code of the country this alert's store entry belongs to (e.g. 'us', 'ca', 'gb').",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "country_name": {
+            "description": "Country name in English, e.g. 'United States'.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "created_on": {
+            "description": "UTC timestamp when the user created the alert.",
+            "format": "date-time",
+            "type": "string"
+          },
+          "last_notified_on": {
+            "description": "UTC timestamp of the last notification sent for this alert. Null/absent when it has never fired.",
+            "format": "date-time",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "last_notified_value": {
+            "description": "The rate or discount percent that triggered the last notification. Null/absent when the alert has never fired.",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "store_id": {
+            "description": "GotCashback's numeric store identifier. Pass it as store_id to set_store_alert, remove_store_alert and the *_by_store_id tools.",
+            "type": "integer"
+          },
+          "store_name": {
+            "description": "Store (retailer) name as shown on GotCashback.",
+            "type": "string"
+          },
+          "threshold_percent": {
+            "description": "The alert fires when the rate or discount reaches this percent or higher (10 means 10%).",
+            "type": "number"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

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 cover readOnly/idempotent/destructive safety, and the description adds meaningful context beyond them: OAuth sign-in requirements, the 'alerts' scope, anonymous-caller authorization behavior, and the exact payload shape. This gives the agent a clear picture of side effects and prerequisites.

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 three sentences and every sentence earns its place: first the core function, then when to use it, then output fields and auth requirements. It is dense but not bloated, and the most decision-relevant information is front-loaded.

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 zero-parameter, read-only, idempotent tool with annotations and an output schema already present, the description covers everything an agent needs: purpose, usage context, return fields, downstream interoperability, and authorization prerequisites. Nothing material is missing.

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 tool has zero parameters and an empty schema, so schema coverage is trivially 100%. The 0-parameter baseline of 4 applies, and the description's output-field details compensate for any need to understand what the no-input call returns.

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 opens with a specific verb and resource: 'Returns the signed-in user's cashback and gift card alerts.' This clearly distinguishes it from sibling tools like get_my_favorite_stores and get_my_profile, and it even names the alert_type values that scope the resource.

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?

The description gives explicit use cases: 'what alerts do I have?' and 'before changing an alert.' It also names downstream sibling tools (set_store_alert, remove_store_alert) whose parameters can be filled directly from the returned values. It doesn't state exclusions, but no competing read-alerts sibling exists.

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?