Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

boardgamegeek_media

Read-only

List one page of images, videos or files for one BoardGameGeek item and return each media record's identity, URLs and metadata. type is image, video or file (default image); per-kind filters are validated locally: sort applies to images, videos and files, image license and interval/tag are image-only, video gallery/language and file language are kind-specific, and a wrong-kind filter is a 400. showcount is 1 to 50 and pageid is 1 to 1000; unknown ids are a 404 and a page past the end is a valid empty result.

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

Input Schema

NameRequiredDescriptionDefault
idYesRequired positive BoardGameGeek item id.
tagNoOptional image tag: BoxFront, BoxBack, Components, Customized, Play, Miscellaneous or uncat. Only valid for images.
sortNoOptional sort order: hot or recent. Applies to images, videos and files.
typeNoOptional media type: image, video or file. Defaults to image.
pageidNoOptional page number, 1 to 1000.
galleryNoOptional gallery filter. Images: all, game, person or creative. Videos: all, review, session, instructional, interview, unboxing, humor or other. Not valid for files.
licenseNoOptional image license filter: reuse, commercial or modify. Omit for any license. Only valid for images.
intervalNoOptional image interval: alltime, today, twodays, last7, last30 or year. Only valid for images.
showcountNoOptional page size, 1 to 50.
languageidNoOptional media language id from boardgamegeek_taxonomy media_video_languages/media_file_languages. Only valid for videos and files.

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

A4/5.0
Behavior4/5

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

Annotations already declare readOnly and openWorld, and the description layers on real behavioral detail beyond them: showcount 1-50, pageid 1-1000, unknown id = 404, and an out-of-range page returning a valid empty result rather than an error. Auth requirements and rate limits are not mentioned, keeping it below the top mark.

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?

Tight and front-loaded: the first sentence states what is returned, then the remainder is a compressed rule set with no filler. The middle sentence is a long run-on of filter clauses that is dense but still parseable.

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 10-parameter listing tool with a 100%-covered schema and an output schema, little is missing; pagination bounds and error semantics cover the main risks. Minor gap is the absence of any note on how this differs from the other BoardGameGeek retrieval tools.

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 genuinely adds cross-parameter semantics the schema states only piecemeal: it consolidates which filters bind to image, video, or file and specifies that a kind mismatch is rejected with a 400. That is meaning an agent could not reliably infer from the per-property text alone.

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?

Opens with a specific verb and resource: 'List one page of images, videos or files for one BoardGameGeek item', plus what each record carries (identity, URLs, metadata). The scope (single item, single page) is unambiguous, but nothing in the text distinguishes it from sibling tools that also fetch media, so it stops short of a 5.

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 concrete operational guidance: type defaults to image, sort applies to all kinds, image-only and kind-specific filters are named, and a wrong-kind filter yields a 400. That effectively tells the agent which filter combinations are legal, but there is no explicit statement of when to reach for this tool versus another BGG retrieval tool.

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

All Crawlora MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources