Skip to main content
Glama
Sign In
untappd-mcp

untappd-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get venues a user has checked in at

untappd_user_venues
Read-onlyIdempotent

Retrieve the venues a user has checked in at, ordered most recent first, with visit dates and check-in counts. Paginate any public or friend account beyond the ~50 check-in cap.

Instructions

Get the venues a user has checked in at, most recent first, with per-venue first/recent visit and check-in counts. Pages fully for any public/friend account (unlike user check-ins, which stop at ~50 for other users). Untappd returns at most 25 venues per page whatever limit you ask for — advance by the returned pagination offset. Omit username for your own account. Read-only.

Input Schema

NameRequiredDescriptionDefault
sortNoSort order (default most recent). Untappd keys: date, recent, date_asc, venue_name_asc, venue_name_desc, highest_checkin, lowest_checkin. Aliases: name = venue_name_asc, checkin = highest_checkin. highest_rated is deprecated (Untappd has no venue rating sort) and is sent as highest_checkin.
limitNoMax venues (1–50; Untappd caps a page at 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. Changed3 schema fields changedv2.6.1
    • changedInput schema / properties / limit / description
      Previous value: -"Max venues (1–50, default 25)"New value: +"Max venues (1–50; Untappd caps a page at 25)"
    • changedInput schema / properties / sort / description
      Previous value: -"Sort order (default most recent)"New value: +"Sort order (default most recent). Untappd keys: date, recent, date_asc, venue_name_asc, venue_name_desc, highest_checkin, lowest_checkin. Aliases: name = venue_name_asc, checkin = highest_checkin. highest_rated is deprecated (Untappd has no venue rating sort) and is sent as highest_checkin."
    • changedInput schema / properties / sort / enum
      Previous value: -[
-  "date",
-  "name",
-  "checkin",
-  "highest_rated"
-]New value: +[
+  "date",
+  "recent",
+  "date_asc",
+  "venue_name_asc",
+  "venue_name_desc",
+  "highest_checkin",
+  "lowest_checkin",
+  "name",
+  "checkin",
+  "highest_rated"
+]
  2. 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"
  3. Addedv1.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds genuinely non-obvious behavior: a hard 25-venues-per-page cap regardless of requested limit, and the need to advance by the returned pagination offset. It does not describe error or auth-failure behavior, keeping it short of a 5.

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?

Four tight sentences, front-loaded with what the tool returns, then the paging caveat, then the account shortcut, then the read-only note. No filler and no repetition of the title.

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 no output schema, the description still names the returned fields (first/recent visit, check-in counts) and the ordering. Combined with the paging cap and offset guidance, an agent has everything needed to call and iterate 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 the baseline is 3, but the description adds operational meaning: the default sort is most recent, and paging must follow the returned offset rather than a computed one. The username omission rule is restated from the schema, which limits the added value slightly.

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?

States a specific verb and resource ('Get the venues a user has checked in at') plus the ordering and payload shape (per-venue first/recent visit and check-in counts). It explicitly distinguishes itself from the sibling untappd_user_checkins by contrasting paging behavior, so an agent can pick between them without opening a schema.

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?

Gives clear operating context: omit username for your own account, and it pages fully for public/friend accounts unlike user check-ins. It does not explicitly route to untappd_venue_info or untappd_sync_user_venues, so the when-not guidance is partial rather than exhaustive.

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