Skip to main content
Glama
chrischall

untappd-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Check in a beer on Untappd

untappd_checkin
Destructive

Publish a beer check-in to your Untappd feed with optional rating, comment, venue, and photo, after a preview and confirmation step.

Instructions

Post a NEW beer check-in to YOUR Untappd account — this publishes to your public feed. Provide the beer id (bid) from untappd_search_beer; optionally a rating (0–5 in 0.25 steps), a shout (comment), a venue via foursquare_id, and a local photo via photo_path (JPEG/PNG). The preview shows the exact fields and photo that will be posted. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bidYesUntappd beer id to check in (from untappd_search_beer)
shoutNoOptional shout / comment text for the check-in
geolatNoOptional latitude of the check-in
geolngNoOptional longitude of the check-in
ratingNoRating 0–5 in 0.25 increments (omit for no rating)
timezoneNoThe drinker's IANA timezone (e.g. America/New_York), which sets the check-in's local time. Defaults to UNTAPPD_TIMEZONE, else the server's own zone — which on a hosted connector is usually UTC, so pass it when you know where the user is.
photo_pathNoOptional path to a local JPEG/PNG photo (max 15 MB) to attach — it is published publicly. It must be inside the photo directory (UNTAPPD_PHOTO_DIR, default ~/Downloads/untappd-mcp). Only use a file the user explicitly chose; the preview shows the resolved path and size for them to confirm.
confirmTokenNoONLY for the two-step confirmation fallback (a client without MCP elicitation). The confirmToken from this same tool's phase-1 "confirmation-required" response, passed back ONLY after the user has seen that preview and explicitly approved it in chat — never on the first call, never invented, never reused. Call again with the same arguments. Ignored when the client supports elicitation.
container_idNoOptional serving container id (e.g. 1 = draft, 2 = bottle, 3 = can)
foursquare_idNoOptional Foursquare venue id to tag the check-in location

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.3.2
    • changedInput schema / properties / photo_path / description
      Previous value: -"Optional path to a local JPEG/PNG photo (max 15 MB) to attach — it is published publicly. Only use a file the user explicitly chose; the preview shows the resolved path and size for them to confirm."New value: +"Optional path to a local JPEG/PNG photo (max 15 MB) to attach — it is published publicly. It must be inside the photo directory (UNTAPPD_PHOTO_DIR, default ~/Downloads/untappd-mcp). Only use a file the user explicitly chose; the preview shows the resolved path and size for them to confirm."
  2. Changed3 schema fields changedv2.2.1
    • removedInput schema / properties / confirm
      Removed value: -{
-  "description": "Must be true to proceed. Without this, the tool returns a preview.",
-  "type": "boolean"
-}
    • addedInput schema / properties / confirmToken
      Added value: +{
+  "description": "ONLY for the two-step confirmation fallback (a client without MCP elicitation). The confirmToken from this same tool's phase-1 \"confirmation-required\" response, passed back ONLY after the user has seen that preview and explicitly approved it in chat — never on the first call, never invented, never reused. Call again with the same arguments. Ignored when the client supports elicitation.",
+  "type": "string"
+}
    • changedInput schema / properties / photo_path / description
      Previous value: -"Optional path to a local JPEG/PNG photo (max 15 MB) to attach — it is published publicly. Only use a file the user explicitly chose; the dry run shows the resolved path and size for them to confirm."New value: +"Optional path to a local JPEG/PNG photo (max 15 MB) to attach — it is published publicly. Only use a file the user explicitly chose; the preview shows the resolved path and size for them to confirm."
  3. Changed2 schema fields changedv2.1.3
    • changedInput schema / properties / photo_path / description
      Previous value: -"Optional path to a local JPEG/PNG photo to attach to the check-in"New value: +"Optional path to a local JPEG/PNG photo (max 15 MB) to attach — it is published publicly. Only use a file the user explicitly chose; the dry run shows the resolved path and size for them to confirm."
    • addedInput schema / properties / timezone
      Added value: +{
+  "description": "The drinker's IANA timezone (e.g. America/New_York), which sets the check-in's local time. Defaults to UNTAPPD_TIMEZONE, else the server's own zone — which on a hosted connector is usually UTC, so pass it when you know where the user is.",
+  "minLength": 1,
+  "type": "string"
+}
  4. 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"
  5. Changed1 schema field changedv1.0.0
    • addedInput schema / properties / photo_path
      Added value: +{
+  "description": "Optional path to a local JPEG/PNG photo to attach to the check-in",
+  "type": "string"
+}
  6. First observedv0.0.0

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=true, openWorldHint=true, idempotentHint=false), the description discloses that the post is public, that a preview is generated showing exact fields and photo, and the precise two-phase confirmToken contract including 'never on the first call, never invented, never reused'. This is exactly the extra behavioral context annotations cannot carry.

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?

Front-loaded with purpose, then quickly moves to optional fields and the confirmation mechanics; every sentence carries information. It is dense and slightly long, but there is little filler.

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?

With 10 parameters, a required confirmation flow and no output schema, the description still covers the return/preview behavior and the token fallback, which is what an agent needs to drive the call correctly. Remaining parameter detail is fully covered by the schema.

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, but the description adds real meaning: the rating step granularity (0-5 in 0.25 steps), that venue is supplied via foursquare_id, and the photo_path constraints (JPEG/PNG, inside UNTAPPD_PHOTO_DIR, must be user-chosen). It omits any discussion of geolat/geolng, container_id and timezone, which the schema documents instead.

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 first sentence states a specific verb and resource ('Post a NEW beer check-in to YOUR Untappd account') plus the side effect that it publishes to a public feed. It names the sibling it depends on (untappd_search_beer for the bid) and is clearly distinguishable from untappd_delete_checkin / untappd_checkin_info.

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?

It says where the required bid comes from, which fields are optional, and lays out the confirmation workflow (elicitation prompt where supported, otherwise preview + confirmToken retry). It does not explicitly state when not to use the tool (e.g. versus untappd_sync_checkins for historical entries), but the context it gives is clear and actionable.

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