Skip to main content
Glama
chrischall

untappd-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Search Untappd beers

untappd_search_beer
Read-onlyIdempotent

Search Untappd by beer name to find matching beers with brewery, style, ABV, IBU, and rating. Use returned beer IDs to fetch full details.

Instructions

Search Untappd for beers by name (optionally "Brewery Beer"). Returns ranked matches with their beer id (bid), brewery, style, ABV, IBU, and global rating. Feed a bid into untappd_beer_info for full detail. Read-only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoSort order: checkin (relevance, default), name, or count
viewNoResponse shape: "compact" (default) drops fields the response already carries elsewhere; "full" returns every field this server understands. compact projects each match to {bid, name, style, abv, ibu, brewery, checkin_count, have_had}; "full" returns Untappd's whole ~1.2 KB search item, including the long beer_description and the nested brewery record.
limitNoMax results (1–50, default 25)
queryYesBeer name to search for
offsetNoResult offset for paging (default 0)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.0.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 changedv1.10.1
    • removedInput schema / properties / compact
      Removed value: -{
-  "description": "Project each result to a slim summary (bid, name, brewery, style, abv, ibu, counts) to save context (default false)",
-  "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 projects each match to {bid, name, style, abv, ibu, brewery, checkin_count, have_had}; \"full\" returns Untappd's whole ~1.2 KB search item, including the long beer_description and the nested brewery record.",
+  "enum": [
+    "compact",
+    "full"
+  ],
+  "type": "string"
+}
  3. Changed1 schema field changedv1.1.0
    • addedInput schema / properties / compact
      Added value: +{
+  "description": "Project each result to a slim summary (bid, name, brewery, style, abv, ibu, counts) to save context (default false)",
+  "type": "boolean"
+}
  4. First observedv0.0.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, and open-world behavior. The description adds useful context beyond those: results are ranked matches carrying a compact field set, and the search response is intentionally not the full detail record—that is delegated to untappd_beer_info. It also restates 'Read-only' consistently without contradicting 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, front-loaded sentences: what it searches, what it returns, and where to go next. Every sentence adds value and there is no redundant repetition of schema details.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description properly enumerates the returned fields and the follow-up action for details. The input schema fully documents all parameters and defaults, leaving the agent with everything needed to select and invoke the tool correctly.

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 the useful 'Brewery Beer' query format hint and clarifies the response includes ranked matches with specific fields, which enriches the query parameter semantics beyond the schema's generic 'beer name to search for'.

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 clearly states the tool searches Untappd for beers by name, optionally in 'Brewery Beer' format, and lists the exact fields returned. This distinguishes it from sibling tools like untappd_search_brewery and untappd_beer_info, with an explicit pointer to untappd_beer_info for full detail.

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 a clear usage context: use this to find beers by name, then feed a returned bid into untappd_beer_info for full detail. It does not explicitly enumerate when not to use sibling search tools, but the 'Brewery Beer' hint and the routing to beer_info provide clear practical guidance.

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