Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

boardgamegeek_geeklists

Find BoardGameGeek geeklists linked to an object; filter by category, sort by hot or recent, and return titles, authors, item counts, and dates.

Instructions

List geeklists that link a BoardGameGeek object. Returns one page of the community geeklists that link an object, filtered by category (all, trade, general) and sorted by hot or recent. Each row carries the list title, author, item count, recommendation count and dates. The response includes the category filters the source offers and the list totals. Use boardgamegeek_geeklist and boardgamegeek_geeklist_items to read a list's content.

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": {
      "objectid": "<objectid>"
    },
    "name": "boardgamegeek_geeklists"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNoSort: hot or recent. Defaults to hot.
pageidNoPage number, 1-1000
categoryNoCategory filter: all, trade or general. Defaults to general.
objectidYesObject identifier, positive integer; Catan is 13
showcountNoPage size, 1-50
objecttypeNoObject type: thing, family, person, company, property or version. Defaults to thing.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does reasonably well: it discloses pagination ('one page'), the available filter dimensions, sorting behavior, and that totals and the source's offered category filters are returned. It does not mention rate limits or auth, but the read-only nature is evident from 'List'.

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?

Four sentences, front-loaded with the core action and scoped with filters and the row/response shape before the sibling routing sentence. Slight redundancy with the schema's enum lists, but nothing is wasted.

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?

There is no output schema, so the description's enumeration of row fields (title, author, item count, recommendation count, dates) plus list totals is doing necessary work. The only gap is guidance on multi-page traversal, which the schema's pageid/showcount bounds partially cover.

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 every parameter already carries a description, enum values and default. The description restates the category and sort dimensions but adds no syntax, format, or edge-case meaning (e.g., interaction between showcount and pageid limits) beyond the schema.

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

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'List geeklists that link a BoardGameGeek object,' then scopes it to one page filtered by category and sort. It is clearly distinguishable from boardgamegeek_geeklist and boardgamegeek_geeklist_items, which the description explicitly assigns to reading list content.

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

Usage Guidelines4/5

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

The closing sentence explicitly routes the agent: use boardgamegeek_geeklist / boardgamegeek_geeklist_items to read a list's content, implying this tool is for discovering which lists reference an object. It stops short of stating exclusions or when this tool is the wrong choice, but the positive context is clear.

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