Skip to main content
Glama
chrischall

groupon-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

groupon_get_deal

Read-only

Fetch a Groupon deal by permalink slug or full URL to get title, merchant, price, rating, and options; request full view for complete records.

Instructions

Fetch a single Groupon deal by its permalink slug (or full deal URL). Returns the slim projection by default (title, subtitle, merchant, price, rating, division, url, and every option's id/title/price/isSoldOut — pass an option id to groupon_purchase); set view="full" for Groupon's whole record.

Input Schema

NameRequiredDescriptionDefault
viewNoResponse shape: "compact" (default) drops fields the response already carries elsewhere; "full" returns every field this server understands. compact returns the slim projection; "full" returns Groupon's whole records.
dealIdYesDeal permalink slug (e.g. "enset-productions-and-ventures-3") OR a full Groupon deal URL — the last path segment is used.
optionIdNoOptional deal option id to focus on.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.8
    • changedInput schema / properties / view / description
      Previous value: -"Response shape: \"compact\" (default) drops fields the response already carries elsewhere; \"full\" returns every field this server understands. compact returns the slim projection where one exists and strips image URLs elsewhere; \"full\" returns Groupon's whole records."New value: +"Response shape: \"compact\" (default) drops fields the response already carries elsewhere; \"full\" returns every field this server understands. compact returns the slim projection; \"full\" returns Groupon's whole records."
  2. 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"
  3. Changed2 schema fields changedv0.3.0
    • removedInput schema / properties / compact
      Removed value: -{
-  "default": false,
-  "description": "Return a slim projection instead of the full deal.",
-  "type": "boolean"
-}
    • addedInput schema / properties / view
      Added value: +{
+  "description": "Response shape: \"compact\" (default) drops fields the response already carries elsewhere; \"full\" returns every field this server understands. compact returns the slim projection where one exists and strips image URLs elsewhere; \"full\" returns Groupon's whole records.",
+  "enum": [
+    "compact",
+    "full"
+  ],
+  "type": "string"
+}
  4. First observedv0.1.2

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=true), so the bar is lower. The description adds real value by disclosing the default response shape and enumerating the fields returned, plus what view="full" changes — return behavior the annotations don't cover. It omits auth/rate-limit and error behavior, so not a 5.

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?

Purpose is front-loaded in the first clause, with response-shape details following. Dense parentheticals make the middle heavy, but every sentence carries information; nothing is filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so describing the returned projection is essential and the description does it. Identifier formats and view modes are covered for this 3-param tool. Missing only failure behavior for bad slugs/URLs.

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%, so the baseline is 3. The description goes beyond restating the schema by tying optionId to a downstream action (groupon_purchase) and by describing what the default view actually yields, adding workflow meaning the schema fields alone don't convey.

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 verb (fetch) and resource (a single Groupon deal) plus the accepted identifier forms (permalink slug or full URL). This clearly separates it from groupon_search_deals, which would be the plural/discovery counterpart.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description routes forward by noting an option id can be passed to groupon_purchase, which is useful workflow context. However, it never states when to use this tool versus groupon_search_deals (i.e. only when you already hold a slug/URL), leaving the primary selection decision implied.

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