Skip to main content
Glama
chrischall

groupon-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

groupon_search_deals

Read-only

Find Groupon deals in any city by keyword or category. Get compact summaries or full deal details for local, goods, and travel offers.

Instructions

Search or browse Groupon deals for a city (division). Pass query for a free-text search (e.g. "massage", "pizza"); omit it for a plain category/city browse. Returns slim deal summaries by default; set view="full" for Groupon's whole cards.

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.
limitNoMaximum number of deals to return (1-100).
queryNoFree-text search term (e.g. "massage", "pizza"). Omit for a plain category/city browse.
offsetNoNumber of deals to skip for pagination (0-based).
divisionNoGroupon city slug, e.g. new-york, chicago, syracuse.new-york

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 slim deal summaries instead of full cards (recommended for browsing).",
-  "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?

With readOnlyHint=true already declaring this is a safe read operation, the description adds useful behavioral context: results are slim by default, view='full' changes the response shape, and omitting query switches to browse mode. This goes beyond the annotation without contradicting it.

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 front-loaded sentences convey the core behavior, the query/browse distinction, and the output-shape switch with zero filler. Every clause earns its place.

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?

The description is complete enough for a read-only search tool with richly documented schemas and defaults. It covers the main usage decision (query vs. browse) and the output-shape decision (compact vs. full), though pagination and limits are left to the schema rather than surfaced in the description.

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 all parameters thoroughly. The description paraphrases the query/view guidance but does not add 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 names a specific verb ('Search or browse'), a clear resource ('Groupon deals'), and a scope ('for a city (division)'). It also distinguishes the two main modes of this tool (free-text search vs. category/city browse), which separates it from siblings like groupon_get_deal and groupon_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 gives clear conditional guidance: pass `query` for free-text search, omit it for browsing, and use view='full' when full records are needed. It does not explicitly name sibling tools or state when not to use them, so it stops short of a 5, but the internal usage context is unambiguous.

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