untappd-mcp-server

get_venue_checkins

Retrieve recent check-ins at a specific venue to see what's currently on tap.

Instructions

Retrieve the recent check-in feed for a specific venue. Primary tool for 'what's on tap right now' use case.

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

Input Schema

Name	Required	Description
`limit`	No	Number of results (max 25, default 25)
`max_id`	No	Return results older than this checkin ID
`min_id`	No	Return only checkins newer than this ID
`venue_id`	Yes	Untappd venue ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Jul 29, 2026

TDQS

A3.6/5.0

Behavior2/5

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

No annotations are provided, so the description alone must convey behavioral traits. It fails to mention any limits, pagination behavior, rate limits, authentication needs, or response characteristics beyond the basic action.

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?

Two concise sentences with no fluff: first states the function, second gives a clear use case. Every word earns its place.

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

Completeness2/5

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

With no output schema and four parameters including pagination controls, the description should explain the response structure and how parameters like min_id/max_id work. The use case hint is helpful but insufficient for complete agent guidance.

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 coverage is 100%, meaning the input schema already documents all parameters adequately. The description adds no additional meaning beyond the schema, so 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 clearly states the action ('Retrieve') and resource ('recent check-in feed for a specific venue'), and uniquely identifies the tool's use case as 'what's on tap right now', distinguishing it from siblings like get_venue_info or get_beer_checkins.

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 a specific use case ('Primary tool for...'), which implies when to use it, but does not explicitly mention when not to use it or provide alternatives, though the context of sibling tools is available.

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