Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

boardgamegeek_thread

Fetch a BoardGameGeek forum thread and one page of its articles, including metadata, post bodies, and author details, to inspect discussions or moderate content.

Instructions

Get a BoardGameGeek thread and one page of its articles. Returns a forum thread's metadata (subject, forum id, creator, post/page counts, pin/lock flags, breadcrumbs) plus one page of its articles: article id, author id, post and edit dates, plain-text body, rendered bodyXml, first-post flag and links. The source pages articles 25 at a time; a page past the end is a valid empty page. Use boardgamegeek_threads to discover thread ids.

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

Input Schema

Name	Required	Description	Default
`id`	Yes	BoardGameGeek thread id, positive integer
`pageid`	No	Article page number, 1-1000; the source pages articles 25 at a time

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.17.20Nov 12, 2026

TDQS

A4.4/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 well: it discloses the 25-articles-per-page pagination model, the empty-page edge case, and the exact shape of returned data. It omits auth requirements and rate limits, which keeps it from a 5.

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 and return summary, then the sibling pointer last. The return-field enumeration is dense but each item is informative; it is slightly long but no sentence is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 must describe return values, and it does so thoroughly (metadata fields plus article fields). Combined with the pagination and empty-page semantics, an agent has everything needed to call it correctly.

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 coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema by explaining that pageid beyond the end yields a valid empty page and by restating the 25-per-page paging unit in context of the return payload.

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 ('Get a BoardGameGeek thread and one page of its articles') and enumerates the returned metadata and article fields, so an agent can distinguish it from boardgamegeek_threads, which is explicitly named as the id-discovery tool.

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?

Explicitly routes id discovery to boardgamegeek_threads and clarifies that a page past the end is a valid empty page rather than an error. It stops short of stating when-not-to-use conditions, but the primary alternative is named with its selecting condition.

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

Deploy Server