Skip to main content
Glama
chrischall

untappd-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get Untappd user wishlist

untappd_user_wishlist
Read-onlyIdempotent

Retrieve a user's Untappd wishlist beers with sorting and paging. Omit username to access your own wishlist.

Instructions

Get the beers on a user's wishlist. Supports sorting and paging. Omit username for your own account. Read-only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoSort order (default date added, newest first)
viewNoResponse shape: "compact" (default) drops fields the response already carries elsewhere; "full" returns every field this server understands. compact projects each wishlisted beer to {bid, name, style, abv, ibu, brewery, added_at}; "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, added_at) 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 wishlisted beer to {bid, name, style, abv, ibu, brewery, added_at}; \"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, added_at) to save context (default false)",
+  "type": "boolean"
+}
  4. First observedv0.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already provide readOnlyHint=true and idempotentHint=true, lowering the description's burden. The description adds useful behavioral context beyond annotations: it explicitly says "Read-only" and explains the username omission behavior for the configured account. It does not contradict the 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 short sentences with no filler. The core purpose is front-loaded, and the additional behavioral notes about sorting, paging, and omitting username each carry useful information without redundancy.

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?

Considering the moderate complexity of five optional parameters, full schema documentation, and read-only/idempotent annotations, the description is nearly complete for safe invocation. The main absence is a summary of the response shape, but the schema's view parameter already describes compact vs full response details.

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%, and every parameter already has detailed descriptions covering defaults, enums, bounds, and semantics. The description only echoes "sorting and paging," adding no meaning beyond what the schema already provides, so a baseline 3 is appropriate.

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 states a specific action and resource: "Get the beers on a user's wishlist." This clearly distinguishes the tool from sibling tools like untappd_user_checkins, untappd_user_beers, and the wishlist mutation tools untappd_wishlist_add/remove.

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 clear context: the tool is for reading a user's wishlist, supports sorting and paging, and omitting username targets the current account. It does not explicitly name alternatives or say when not to use it, but the read-only framing and sibling names make the distinction clear enough.

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