Skip to main content
Glama
chrischall

groupon-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

groupon_purchase

Destructive

Add a Groupon deal option to your cart for checkout after confirmation, verify quantity, and get a checkout URL to complete payment.

Instructions

Add a Groupon deal option to your cart, ready for checkout. Once confirmed it adds the item, re-reads the cart to verify the line quantity, and returns the checkout URL for YOU to complete payment. It CANNOT place the order — Groupon checkout is native Apple/Google Pay, card, or PayPal. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE).

Input Schema

NameRequiredDescriptionDefault
dealIdYesDeal permalink slug (e.g. "versailles-massage-bar-1") OR a full Groupon deal URL — the last path segment is used.
isGiftNoMark the line item as a gift.
optionIdNoWhich deal option to buy (an option id from groupon_get_deal). Required when the deal has more than one option; may be omitted for a single-option deal.
quantityNoHow many to add (1-10, default 1).
confirmTokenNoONLY for the two-step confirmation fallback (a client without MCP elicitation). The confirmToken from this same tool's phase-1 "confirmation-required" response, passed back ONLY after the user has seen that preview and explicitly approved it in chat — never on the first call, never invented, never reused. Call again with the same arguments. Ignored when the client supports elicitation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.1.8
    • changedInput schema / properties / quantity / description
      Previous value: -"How many to add (default 1)."New value: +"How many to add (1-10, default 1)."
    • changedInput schema / properties / quantity / maximum
      Previous value: -9007199254740991New value: +10
  2. Changed2 schema fields changedv1.1.1
    • removedInput schema / properties / confirm
      Removed value: -{
-  "description": "Must be true to proceed. Without this, the tool returns a preview.",
-  "type": "boolean"
-}
    • addedInput schema / properties / confirmToken
      Added value: +{
+  "description": "ONLY for the two-step confirmation fallback (a client without MCP elicitation). The confirmToken from this same tool's phase-1 \"confirmation-required\" response, passed back ONLY after the user has seen that preview and explicitly approved it in chat — never on the first call, never invented, never reused. Call again with the same arguments. Ignored when the client supports elicitation.",
+  "type": "string"
+}
  3. Changed1 schema field changedv1.0.2
    • changedInput schema / properties / optionId / description
      Previous value: -"Which deal option to buy (an option id from groupon_get_deal). Defaults to the first option."New value: +"Which deal option to buy (an option id from groupon_get_deal). Required when the deal has more than one option; may be omitted for a single-option deal."
  4. Changed1 schema field changedv0.4.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  5. First observedv0.1.2

TDQS

A4.4/5.0
Behavior5/5

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

Annotations establish a mutating, destructive, open-world operation; the description goes well beyond by disclosing the post-add cart re-read/quantity verification, the returned checkout URL, the payment boundary, and the full two-step confirmation/confirmToken fallback tied to MCP_CONFIRM_MODE. This is unusually rich operational context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the primary action and scope before the confirmation mechanics, and every sentence carries distinct information. It is dense and slightly long, but no sentence is filler.

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 correctly supplies the return contract (checkout URL) and the verification behavior. An agent has enough to call it correctly, including the confirmation protocol. Nothing material is missing.

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 already 100%, so all five parameters are documented in the schema. The description's confirmToken/MCP_CONFIRM_MODE sentence largely restates what the schema's confirmToken field already explains, adding little new syntax or constraint detail beyond the baseline.

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?

Opens with a specific verb+resource ('Add a Groupon deal option to your cart') and immediately bounds the scope with 'ready for checkout' and 'CANNOT place the order'. This clearly separates it from siblings like groupon_view_cart, groupon_get_deal, and groupon_clear_cart.

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?

Gives strong when-to-use context (cart-adding before checkout) and explicit when-not (cannot place the order; payment is native Apple/Google Pay, card, or PayPal). It also routes to groupon_get_deal by referencing option ids, though it never explicitly names a sibling tool for that lookup.

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

Deploy Server

Other Tools