Skip to main content
Glama
chrischall

groupon-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

groupon_get_deal

Read-only

Fetch a Groupon deal's details using its permalink slug or full URL. Returns title, price, rating, merchant, and option summaries in compact or full view.

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, option summaries, url); 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. 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"
+}
  2. First observedv0.1.2

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds meaningful behavior beyond that: it defaults to a slim projection, accepts either a slug or full URL, and documents that view='full' returns Groupon's whole record. It does not detail error cases, but for a simple read-only fetch this is sufficient and it does not contradict the annotations.

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?

The description is two sentences with no filler. It front-loads the action and resource, then states the default return shape and the way to get the full record, earning its place in every clause.

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?

For a read-only single-item fetch with annotations covering safety and the schema covering both parameters, the description is nearly complete. It lists the slim projection fields and the full-record switch, though it does not discuss invalid IDs or when to prefer search_deals, which are minor gaps.

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?

The input schema already fully documents dealId as 'Deal permalink slug, or full deal URL' and describes the view enum and its effects in detail. The description reinforces the slug/URL behavior and the default slim vs. full distinction, but adds little semantic meaning beyond what the schema provides, so the baseline of 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 uses a specific verb ('Fetch a single Groupon deal') and resource identifier ('permalink slug or full deal URL'), and lists the fields returned in the slim projection. This clearly distinguishes it from sibling tools like search_deals or list_categories.

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?

The description makes the intended use clear: use this when you already have a known deal permalink slug or full URL and want the complete or slim deal record. It doesn't explicitly exclude search_deals for query-based discovery, but the emphasis on 'a single deal' and the URL-based key provides unambiguous context.

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