Skip to main content
Glama
chrischall

untappd-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get Untappd distinct beers

untappd_user_beers
Read-onlyIdempotent

Retrieve every unique beer a user has checked in, including personal ratings and check-in counts. Sort and page through results to explore drinking history. Omit username to view your own account.

Instructions

Get the distinct (unique) beers a user has ever checked in, with their rating and check-in count per beer. Supports sorting and paging. Omit username for your own account. Read-only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoSort order (default date, most recent first)
viewNoResponse shape: "compact" (default) drops fields the response already carries elsewhere; "full" returns every field this server understands. compact projects each distinct beer to {bid, name, style, abv, ibu, brewery, your_count, your_rating, global_rating, last_had}; "full" returns Untappd's whole ~1.2 KB beer record per entry, including the long beer_description and the nested brewery record.
limitNoMax beers (1–50, default 25)
offsetNoResult offset for paging (default 0)
usernameNoUntappd username. Omit to use your own configured account (UNTAPPD_USERNAME).

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 beer to a slim summary (bid, name, brewery, style, abv, ibu, your_count, your_rating, global_rating, last_had) 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 distinct beer to {bid, name, style, abv, ibu, brewery, your_count, your_rating, global_rating, last_had}; \"full\" returns Untappd's whole ~1.2 KB beer record per entry, 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 beer to a slim summary (bid, name, brewery, style, abv, ibu, your_count, your_rating, global_rating, last_had) to save context (default false)",
+  "type": "boolean"
+}
  4. First observedv0.0.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, and the description repeats 'Read-only.' It adds some useful context about deduplication and defaulting to the configured account, but does not disclose rate limits, pagination behavior beyond the schema, or any subtle aggregated-response behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise and front-loaded with the core purpose before secondary details like sorting/paging. The final 'Read-only.' is redundant with the readOnlyHint annotation, so it is not strictly earning its place, but the overall structure is efficient.

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 aggregation tool with well-described parametershebdomad, the description covers the essential behavior: distinct beers, rating/count, sorting, paging, and self-account default. There is no output schema, so a bit more return-shape detail beyond the 'view' parameter would have been ideal, but the included preview and compact/full field list in the schema fill most of the gap.

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 fully documents all five parameters. The description's mention of sorting, paging, and omitting username largely mirrors what the schema already provides, adding no meaningful new semantic value beyond a brief summary.

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 ('Get'), resource ('distinct beers a user has ever checked in'), and the key returned data ('rating and check-in count per beer'). It clearly differentiates from siblings like untappd_user_checkins by emphasizing unique beers rather than individual check-ins.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives a clear usage hint for omitting username when targeting the configured account, and mentions sorting/paging. However, it does not explicitly state when to prefer this tool over closely related siblings such as untappd_user_checkins or untappd_sync_user_beers.

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