Skip to main content
Glama
chrischall

untappd-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get recent check-ins for a beer

untappd_beer_activity
Read-only

Fetch recent public check-ins for a beer by its Untappd ID (bid), showing who drank it, their rating, comment, and venue. Supports paging with max_id for older check-ins.

Instructions

Get the recent public check-ins for a beer by its bid — who drank it, their rating, comment, and venue. Page backwards with max_id (the pagination.max_id from a prior call). Read-only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bidYesUntappd beer id (bid)
viewNoResponse shape: "compact" (default) drops fields the response already carries elsewhere; "full" returns every field this server understands. compact projects each check-in to {id, user, beer, brewery, venue, rating, comment, toast/comment counts}; "full" returns Untappd's whole ~5 KB record.
limitNoMax check-ins (1–50, default 25)
max_idNoReturn check-ins older than this id (for paging)

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 check-in to a slim summary (id, user, beer, rating, comment, venue, toast/comment 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 check-in to {id, user, beer, brewery, venue, rating, comment, toast/comment counts}; \"full\" returns Untappd's whole ~5 KB record.",
+  "enum": [
+    "compact",
+    "full"
+  ],
+  "type": "string"
+}
  3. Changed1 schema field changedv1.1.0
    • addedInput schema / properties / compact
      Added value: +{
+  "description": "Project each check-in to a slim summary (id, user, beer, rating, comment, venue, toast/comment counts) to save context (default false)",
+  "type": "boolean"
+}
  4. Addedv1.0.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description reinforces this with 'Read-only.' It also adds useful behavioral context beyond the schema: check-ins are public, paging is backwards using max_id, and max_id comes from a prior call's pagination data. This gives the agent a clear mental model of how the endpoint behaves.

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?

The description is two focused sentences with no filler. It front-loads the action and resource, then packs the key behavioral details (paging, max_id source, read-only) into the second sentence. Every phrase 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?

There is no output schema, so the description partially compensates by listing the returned fields (user, rating, comment, venue) and explaining paging. It is adequate for an agent to call the tool correctly, though it could additionally note that results are ordered or that 'comment' may be absent for some check-ins.

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 coverage is 100% and every parameter (bid, view, limit, max_id) already has a meaningful description. The main description adds only a slight clarification about max_id coming from prior pagination, which is helpful but does not substantially add beyond what the schema already documents.

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 ('Get'), a specific resource ('recent public check-ins for a beer'), and an identifier ('bid'), making the tool's purpose immediately clear. It also lists what the response contains (user, rating, comment, venue), which distinguishes it from beer metadata tools like untappd_beer_info.

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 clearly implies when to use it: whenever you need recent check-in activity for a specific beer. However, it does not explicitly name alternatives or state when not to use it, such as choosing untappd_checkin_info for a single check-in, untappd_user_checkins for a user's activity, or untappd_venue_activity for venue-level activity.

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