Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

boardgamegeek_threads

Lists a BoardGameGeek object's forum threads sorted by hot, recent, or active, returning thread details and available forums so you can filter by forumid and paginate results.

Instructions

List a BoardGameGeek object's forum threads. Returns one page of forum threads for a BoardGameGeek object (game, family, person, company, property or version), sorted by hot, recent or active. Each row carries the thread id, subject, forum, author, post/last-post dates, post count, pin/lock flags and hrefs, and the response includes the forums that object exposes with their thread/post counts so callers can discover the forumid filter. Use boardgamegeek_thread to read a thread's articles.

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

Input Schema

Name	Required	Description
`sort`	No	Thread sort: hot, recent or active. Defaults to recent.
`pageid`	No	Page number, 1-1000
`forumid`	No	Forum id from this route's forums list; unknown ids are ignored upstream, so use a listed id
`objectid`	Yes	Object identifier, positive integer; Catan is 13
`showcount`	No	Page size, 1-100; the source caps it at 100
`objecttype`	No	Object type: thing, family, person, company, property or version. Defaults to thing.

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.17.20Nov 12, 2026

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 full burden and does disclose meaningful behavior: results are one page only, sorting modes, and the shape of each row (id, subject, forum, author, dates, post count, pin/lock flags, hrefs). It omits auth requirements and rate limits, which leaves a gap for a network-backed listing tool.

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?

Front-loaded with the core action, then scope, then return shape, then the sibling pointer — a sensible order. The middle sentence enumerating row fields is dense but each element is informative; the text is long yet nearly all of it 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?

There is no output schema, and the description compensates by describing both the row payload and the accompanying forums metadata, which is exactly what a caller needs. Combined with 100% schema coverage, the definition is nearly complete; only operational concerns like pagination limits across pages or auth are unstated.

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%, so the parameters are already fully documented, setting the baseline at 3. The description adds one genuinely new insight — that the response's forums list is the source of valid forumid values — but does not otherwise extend parameter meaning 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 a BoardGameGeek object's forum threads') plus scope (one page, per object, sortable by hot/recent/active) and explicitly distinguishes itself from boardgamegeek_thread, which reads a thread's articles. An agent can tell these two apart without inspecting either schema.

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?

Gives an explicit routing rule: use this to enumerate threads for an object, use boardgamegeek_thread to read articles inside a thread. It also tells callers how to obtain a valid forumid via the returned forums list. It stops short of stating when not to use it (e.g. cross-object thread search).

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

Deploy Server