untappd-mcp-server

get_user_stats_at_venue

Scan a user's recent check-in feed to get venue stats: visit count, last visit, average rating, and top beers.

Instructions

Get a user's check-in stats at a specific venue — visit count, last visit, average rating, top beers — by scanning their recent check-in feed (1 API call per 25 check-ins scanned; the stats cover the scanned window, not all time)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "venue_id": "<venue_id>"
    },
    "name": "get_user_stats_at_venue"
  }
}

Input Schema

Name	Required	Description
`username`	No	Untappd username (defaults to UNTAPPD_USERNAME env var)
`venue_id`	Yes	Untappd venue ID
`max_pages`	No	Max feed pages to scan at 25 check-ins/page (default 5 = 125 check-ins)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Jul 29, 2026

TDQS

A4.4/5.0

Behavior4/5

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

With no annotations, the description carries full burden. It discloses API cost ('1 API call per 25 check-ins scanned') and the limitation that stats are window-based. This provides valuable behavioral context beyond the input schema.

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?

A single, well-structured sentence with a dash for listing and a parenthetical for caveats. Every part adds value 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?

No output schema, but description explains what is returned (stats list) and the scanning method. It addresses a key limitation. For a stats tool among many siblings, this is sufficient context.

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%, but the description adds context: username defaults to an env var, max_pages default 5 = 125 check-ins, and the scanning process. This enhances understanding of how parameters affect behavior.

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 clearly states the verb 'Get' and the resource 'user's check-in stats at a specific venue', listing specific data points (visit count, last visit, average rating, top beers). It distinguishes from siblings like get_user_beer_stats and get_venue_checkins by focusing on aggregated stats at a venue.

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 explains the scanning mechanism and that stats cover only the scanned window, not all time. This implies a trade-off between speed and completeness, giving usage context. However, it does not explicitly compare to alternatives or state when-not-to-use.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.