untappd-mcp-server

get_user_info

Fetch profile and statistics for any Untappd user by providing their username. Optionally request compact data excluding checkins and media.

Instructions

Retrieve profile and stats for a specific Untappd user by username

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": {
      "username": "<username>"
    },
    "name": "get_user_info"
  }
}

Input Schema

Name	Required	Description	Default
`compact`	No	If true, returns user info only (no checkins, media, recent brews). Default: false
`username`	Yes	Untappd username to look up

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Jul 29, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations, the description must disclose behavior. It only says 'Retrieve', implying a read-only operation, but it does not mention authentication requirements, rate limits, or the effect of the 'compact' parameter on output.

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?

A single, direct sentence with no wasted words. It is front-loaded and easy to scan, though it omits important details.

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?

Given no output schema and no annotations, the description lacks detail about what 'profile and stats' includes or how the optional 'compact' parameter affects results. This is insufficient for an agent to fully understand the tool's output and behavior.

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%, so baseline is 3. The description adds no extra meaning beyond 'by username'; the 'compact' parameter is not mentioned, so no value added beyond schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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 'profile and stats for a specific Untappd user by username'. It distinguishes this general user info tool from more specific sibling tools like get_user_badge_summary or get_user_activity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives like get_user_badge_summary or get_user_activity. There are no conditions or exclusions mentioned.

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