Skip to main content
Glama

CouponBricks verified coupons

Get tested coupons for a store

get_coupons
Read-only

Live coupon codes and deals for one store, best first: exclusive codes, then codes our team verified most recently. Each offer has the discount, what it applies to, the date our team last verified it at checkout, and either a code to type at checkout or a link the shopper must open first.

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": "get_coupons"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many offers to return (default 6).
storeYesStore name or slug from search_stores.
countryNoShopper's country as a 2-letter code: US, IN, AE, SG, MY or JP. Any other value (or none) uses the CouponBricks global site.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Beyond the readOnly/openWorld annotations, the description discloses the sort order (exclusive codes first, then most recently verified) and distinguishes two redemption paths (typed code vs. link the shopper must open first). That is real behavioral context an agent could not infer from annotations. It omits operational details such as result limits or fallback behavior when no coupons exist.

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?

Two sentences, front-loaded with purpose and ordering, then the shape of each offer. Every clause earns its place with no repetition of schema fields.

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?

With no output schema, the description carries the burden of describing return contents and does so: discount, applicability, last-verified date, and code-or-link. Combined with the ordering rationale, an agent has everything needed to call it and interpret results.

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 coverage is 100%, so store, limit, and country are already fully documented with defaults and allowed values. The description reinforces the single-store scope but adds no meaning about limit or country handling beyond the schema, so the baseline 3 applies.

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 ("Live coupon codes and deals for one store") and states the ordering policy, which makes it immediately distinguishable from search_stores. An agent knows exactly what this returns without opening the schema.

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?

It makes clear the scope is a single store and the schema ties the store argument to search_stores, giving an implicit workflow (find the store first, then fetch coupons). It does not state any when-not-to-use case or explicitly name an alternative to this tool, so it stops short of full routing guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources