Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

boardgamegeek_geeklist_items

Fetch one page of a BoardGameGeek geeklist's entries, returning item summaries, authors, post dates, commentary, rating snapshots, and links for each entry.

Instructions

List a BoardGameGeek geeklist's entries. Returns one page of a geeklist's entries: each entry's id, linked item summary (id, name, href, descriptors, images), author id, post/edit dates, commentary body, optional custom image, rating snapshot and links. The source pages entries 25 at a time; a page past the end is a valid empty page.

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

Input Schema

NameRequiredDescriptionDefault
idYesBoardGameGeek geeklist id, positive integer
pageNoEntry page number, 1-1000; the source pages entries 25 at a time

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does a solid job: it discloses the fixed page size (25 entries), that paging beyond the end returns a valid empty page rather than an error, and the full shape of each returned entry. It stops short of noting auth requirements, rate limits, or what occurs for a nonexistent geeklist id.

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 purpose, then return contents, then the pagination edge case. The long field enumeration is dense but earns its place because there is no output schema; only minor trimming is possible.

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 two-parameter read tool with no output schema and no annotations, the description covers the essentials: what is returned, one entry per record, and the empty-page edge case. Only error behavior for invalid or nonexistent ids is left unspecified.

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 description coverage is 100%, so both 'id' and 'page' are already documented in the schema, including the 25-per-page fact. The description's pagination remark duplicates rather than extends that; the parameter section adds essentially nothing the schema doesn't already say.

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 opens with a specific verb and resource ("List a BoardGameGeek geeklist's entries") and then enumerates what an entry contains, so the agent knows this returns entry rows rather than geeklist metadata. It doesn't explicitly contrast with the sibling 'boardgamegeek_geeklist' tool, which is what keeps it off a 5, but the scope 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: an agent can infer this is the tool to call once it has a geeklist id. There is no statement of when to prefer it over 'boardgamegeek_geeklist' or the other item-listing siblings, and no prerequisites or exclusions are given.

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