Skip to main content
Glama
chrischall

untappd-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get Untappd friend activity feed

untappd_activity_feed
Read-only

Retrieve recent check-ins from people you follow on Untappd, newest first. Page back through older activity using the max_id parameter from a previous response.

Instructions

Get your Untappd friend activity feed — the recent check-ins from people you follow, newest first. Page backwards with max_id (the pagination.max_id from a prior call). Read-only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
viewNoResponse shape: "compact" (default) drops fields the response already carries elsewhere; "full" returns every field this server understands. compact projects each check-in to {id, user, beer, brewery, venue, rating, comment, toast/comment counts}; "full" returns Untappd's whole ~5 KB record.
limitNoMax check-ins (1–50, default 25)
max_idNoReturn check-ins older than this id (for paging)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.0.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed2 schema fields changedv1.10.1
    • removedInput schema / properties / compact
      Removed value: -{
-  "description": "Project each check-in to a slim summary to save context (default false)",
-  "type": "boolean"
-}
    • addedInput schema / properties / view
      Added value: +{
+  "description": "Response shape: \"compact\" (default) drops fields the response already carries elsewhere; \"full\" returns every field this server understands. compact projects each check-in to {id, user, beer, brewery, venue, rating, comment, toast/comment counts}; \"full\" returns Untappd's whole ~5 KB record.",
+  "enum": [
+    "compact",
+    "full"
+  ],
+  "type": "string"
+}
  3. Changed1 schema field changedv1.1.0
    • addedInput schema / properties / compact
      Added value: +{
+  "description": "Project each check-in to a slim summary to save context (default false)",
+  "type": "boolean"
+}
  4. First observedv0.0.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=false, and the description adds meaningful behavior: feed is scoped to followed users, ordered newest-first, and pages backwards using max_id taken from a prior call's pagination.max_id. It also explicitly states 'Read-only,' with no contradiction.

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 sentences with no filler: the first front-loads the purpose and ordering, the second captures the paging mechanism. Every sentence earns its place.

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?

For a read-only list tool with no output schema, it provides sufficient operational detail: scope, ordering, paging direction, and where to obtain max_id. It does not enumerate the full response shape, but the schema fully documents the input options and no essential invocation detail is missing.

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 description coverage is 100% with already-rich parameter docs, providing a baseline of 3. The description adds genuine cross-call semantics by saying max_id is the pagination.max_id from a prior call and that paging goes backward, which goes beyond the schema's 'older than this id' note.

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?

Clear verb+resource: 'Get your Untappd friend activity feed' with 'recent check-ins from people you follow, newest first.' It is obviously distinct from user-centric tools like untappd_user_checkins, but it does not explicitly name or contrast a sibling, so it falls short of 5.

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 intended context is implied: use this when you want the friend activity feed rather than a single user's check-ins. However, there is no explicit when-to-use guidance, exclusions, or mention of alternatives such as untappd_user_checkins, so selection across the long sibling list is left to inference.

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

Deploy Server

Other Tools