Skip to main content
Glama

boardgamegeek_reviews

Read-only

Get List a BoardGameGeek object's reviews. Returns an object's hot and recent reviews as the source publishes them: text review threads (thread id, subject, forum, author, dates, post count) and video reviews (video id, host, external id, title, language, thumbnail), with the source's review totals and the paths to the full review lists. An object with no reviews is a valid empty result, not an error.

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": {
      "type": "<type>",
      "id": "<id>"
    },
    "name": "boardgamegeek_reviews"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesRequired positive object id.
typeYesRequired object type: thing, family, person, company, property or version.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish readOnlyHint and openWorldHint, and the description adds real value beyond them: it characterizes the result as a source-published preview of hot/recent reviews with paths to full lists, and explicitly states that zero reviews is a valid empty result rather than an error. It doesn't cover rate limits or auth needs, but the empty-result contract is exactly the kind of behavioral detail that prevents agent misfires.

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?

Three sentences, front-loaded with the action, followed by return-shape detail and the empty-result caveat. The parenthetical field enumerations are dense but informative; nothing is filler, though the listing of every returned field is slightly over-detailed given an output schema exists.

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 simple two-parameter read tool with a full output schema, the description covers purpose, return contents, and the empty-result edge case. The only gap is how it relates to adjacent thread/media tools, which would require cross-tool guidance the description omits.

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% and both parameters (id, type) are fully annotated in the schema, so the description owes little here and delivers little. It never mentions what 'type' accepts or how it affects retrieval, but with complete schema descriptions the baseline of 3 is appropriate.

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 states a specific verb and resource: get a BoardGameGeek object's reviews, covering both hot and recent reviews. It doesn't explicitly distinguish itself from siblings like boardgamegeek_thread or boardgamegeek_media, so an agent must infer the boundary, but the core purpose is unambiguous.

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?

Usage is only implied by 'an object's reviews' — the agent can infer this is for review content on a BGG entity, with boardgamegeek_thread likely being the alternative for full thread content. No explicit when-to-use, when-not, or named alternative appears in the description.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.