Skip to main content
Glama
chrischall

groupon-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

groupon_get_deal

Read-only

Retrieve a specific Groupon deal by its permalink slug or full URL, returning pricing, options, and merchant details. Choose compact or full view for the complete record.

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

TableJSON 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 where one exists and strips image URLs elsewhere; "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 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"
  2. 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"
+}
  3. First observedv0.1.2

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description is consistent with that safety profile. Beyond the annotation, the description adds valuable behavioral detail: the default slim projection lists its exact fields (title, subtitle, merchant, price, rating, division, url, option id/title/price/isSoldOut) and the view='full' alternative. This exceeds what the annotation conveys.

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 with zero repetition of the schema: the first names the resource and key, the second discloses the default projection, the full-view alternative, and the purchase workflow. Every clause earns its place and the most decision-relevant fact (single deal, fetched by slug) is front-loaded.

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?

With no output schema present, the description compensates by stating the default return shape and listing its fields, plus the full-record alternative. All three parameters are fully documented in the schema and read-only behavior is covered by annotations. Only minor gaps remain (e.g., 404/not-found behavior for bad slugs), which is acceptable for a simple read tool.

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 100%, so the schema already documents dealId (slug/URL, last-path-segment behavior), view (compact vs full), and optionId (optional focus). The description adds one genuinely useful bit — that option IDs are what you pass to groupon_purchase — but the schema carries the bulk of parameter meaning. Baseline 3 is appropriate when the schema does the heavy lifting.

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+resource pair — 'Fetch a single Groupon deal' — and identifies the exact key (permalink slug or full deal URL). This clearly distinguishes it from groupon_search_deals (multi-result search) and groupon_purchase (transactional action). An agent can tell what this does 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 Guidelines3/5

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

The description implies usage context: use this when you have an exact deal slug or URL, and use groupon_purchase when you have an option id from the returned projection. It names groupon_purchase as a downstream step, but never explicitly says 'use groupon_search_deals when you lack a deal identifier' or otherwise contrasts this with sibling tools. The when-to-use is inferable rather than stated.

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