Skip to main content
Glama
chrischall

groupon-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

groupon_purchase

Add a Groupon deal to your cart, verify the quantity, and receive a checkout URL to complete payment yourself. Confirms the selection before adding the item.

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

TableJSON 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 (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.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"
+}
  2. 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."
  3. 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"
  4. First observedv0.1.2

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only mark readOnlyHint=false and openWorldHint=true; the description goes much further by disclosing that the tool re-reads the cart to verify quantity, returns a checkout URL rather than placing the order, and requires user confirmation before adding. It also exposes the token-based two-step fallback behavior.

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?

Around four sentences, each carrying distinct information: core action, post-add verification, payment limitation, and confirmation modes. Front-loaded with the main purpose; no filler. Slightly dense but all content is earned.

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 5-parameter mutation tool with no output schema, the description covers the return value (checkout URL), the verification behavior, the payment limitation, and both confirmation paths. It even references MCP_CONFIRM_MODE for clients without elicitation, so an agent has sufficient context to call it 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?

Schema coverage is 100% with detailed per-parameter descriptions, so the tool description doesn't need to re-elaborate. It adds value by explaining how confirmToken fits the overall two-step flow and how the returned checkout URL relates to the purchase, which helps the agent orchestrate the call sequence.

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?

States a specific action: adds a Groupon deal option to the user's cart. Clearly distinguishes from siblings like groupon_get_deal (fetch) and groupon_view_cart (read-only) by describing the mutation flow and checkout handoff.

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?

Explains the intended use (add to cart, get checkout URL, user completes payment) and the confirmation requirement, including the two-step fallback with confirmToken. It does not explicitly enumerate alternative tools or when-not-to-use, but the context is clear.

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