Skip to main content
Glama
chrischall

groupon-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

groupon_search_deals

Read-only

Search local Groupon deals by city or browse by category; use a query for free-text like 'pizza' or omit it to browse. Returns slim summaries by default, with full view for complete cards.

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

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

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description usefully notes the default response is slim summaries and that view="full" returns whole cards, but that largely restates the schema's own `view` description and adds no auth, rate-limit, or pagination-limit context.

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?

Three short sentences, front-loaded with the core action, then the query branch, then the return shape. No filler and every clause carries information.

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, the description responsibly summarizes what comes back (slim deal summaries vs full cards). Pagination offset/limit defaults live in the schema, so the only minor gap is what a 'deal summary' actually contains.

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 baseline is 3; the description adds value by framing the query/omit branch as a search-vs-browse semantic and by giving concrete query and division examples. The compact/full explanation duplicates the schema rather than extending it.

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+resource+scope: 'Search or browse Groupon deals for a city (division)'. The dual mode (free-text search vs category/city browse) plus city scoping clearly separates it from groupon_get_deal (single 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?

Explicitly tells the agent when to pass `query` (free-text search) and when to omit it (plain category/city browse), which is a real branch decision. It does not, however, mention siblings such as groupon_get_deal for full deal detail or any preconditions.

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