untappd-mcp-server

get_venue_info

Retrieve detailed venue info and recent check-ins by providing an Untappd venue ID. Ideal for exploring venue activity, top beers, and media.

Instructions

Retrieve detailed information and recent check-ins for a known venue

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_venue_info"
  }
}

Input Schema

Name	Required	Description	Default
`compact`	No	If true, returns venue info only (no checkins, media, top_beers). Default: false
`venue_id`	Yes	Untappd venue ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Jul 29, 2026

TDQS

B3.4/5.0

Behavior2/5

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

No annotations are provided, so the description carries full responsibility. It mentions 'recent check-ins' but does not specify the recency limit, number of check-ins, or any behavioral traits like rate limits, authentication needs, or data scope beyond the mention. The compact parameter is not described in the tool description, leaving agents to infer from schema.

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?

The description is a single, clear sentence that is efficient and to the point. It could benefit from slightly more structure but has no unnecessary words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given there is no output schema, the description should explain what 'detailed information' and 'recent check-ins' entail. It does not mention available fields, structure, or pagination. However, for a tool with only two parameters and a clear purpose, it is adequately complete for basic understanding.

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% for both parameters, so the description does not need to add much. It provides no additional meaning beyond what the schema already states about 'venue_id' and 'compact'.

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 'retrieve' and the resource 'detailed information and recent check-ins for a known venue'. It effectively distinguishes itself from sibling tools like 'venue_search' (which finds venues) and 'get_venue_checkins' (which focuses only on check-ins).

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 implies that the tool is for a venue already known (via venue_id), but it does not explicitly state when to use it versus alternatives, nor does it mention prerequisites or conditions. It lacks explicit guidance on 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.