untappd-mcp-server

get_user_badge_summary

Retrieve a structured summary of all badges earned by an Untappd user, automatically paginating through up to 20 pages of 50 badges each.

Instructions

Retrieve all badges for a user (paginating to completion) with a structured summary (costs 1 API call per 50 badges)

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

Input Schema

Name	Required	Description	Default
`username`	Yes	Untappd username
`max_pages`	No	Max pages to scan at 50 badges/page (default 10 = 500 badges)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Jul 29, 2026

TDQS

B3.3/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It discloses pagination behavior and API call cost, which is helpful. However, it lacks details on authentication requirements, error handling, or the structure of the summary output.

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?

The description is a single sentence that front-loads the primary action and includes critical details (pagination, cost). Every word adds value, making it efficient and well-structured.

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, the description should explain what the 'structured summary' contains, such as badge names, categories, or counts. The description omits this, leaving the agent uncertain about the return format. Also, no mention of error scenarios or constraints on the username.

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%, so baseline is 3. The description adds semantic value by explaining 'max_pages' in terms of badge count ('50 badges/page' and 'default 10 = 500 badges'), which clarifies the parameter's effect beyond the schema's description.

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 tool retrieves all badges for a user with pagination and a structured summary. The verb 'retrieve' and resource 'badges' are specific. However, it does not explicitly differentiate from the sibling 'get_user_badges', so clarity is good but not perfect.

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 provided on when to use this tool vs alternatives (e.g., 'get_user_badges' or other user-specific tools). The description does not mention prerequisites, default behavior, or when to adjust 'max_pages'.

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