Skip to main content
Glama
chrischall

groupon-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

groupon_search_deals

Read-only

Find and browse Groupon deals by city. Use a free-text query for specific products or services, or omit it to explore category listings.

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

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds useful behavioral context by disclosing the default return shape ('slim deal summaries') and how to get 'Groupon's whole cards' via view='full'. No contradiction with 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?

Three concise sentences, front-loaded with the core action and resource, then mode guidance, then response-shape behavior. Every sentence adds value and there is no redundancy.

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 search tool with 100% schema coverage, the description covers the main behavioral choices: search vs browse, city scope, and response verbosity. It does not describe error conditions or pagination, but those are adequately covered by the schema and annotations.

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 adds extra meaning beyond the schema by explaining the semantic difference between passing `query` (free-text search) and omitting it (category/city browse), and by framing `division` as the city context.

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 ('Search or browse') and a specific resource ('Groupon deals for a city (division)'). It also distinguishes the two operating modes (free-text query vs category/city browse), which clearly separates this 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 explicit guidance on when to pass `query` versus omit it for a plain browse, and clarifies the default vs 'full' view behavior. It does not explicitly name alternative siblings or state when not to use this tool, but the usage context is clear.

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