Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

xbox_collection

Fetch one page of a curated Xbox collection, such as Top Free Games or Xbox Play Anywhere, using an optional cursor to page through results.

Instructions

Get one page of a curated Xbox collection. Returns one page of a named, editorially curated Xbox collection (e.g. Top Free Games, Top Paid Games, Optimized for Series X|S, Xbox Play Anywhere). Pages forward via an opaque cursor: pass the previous response's next_cursor to fetch the next page. This is a partial, non-exhaustive list of known collection ids -- there is no discovery endpoint for the full set.

Input Schema

NameRequiredDescriptionDefault
idYesCurated collection to fetch
cursorNoOpaque pagination cursor from a previous response's next_cursor
localeNoDisplay locale (BCP-47)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and discloses key traits: it returns a single page, pagination is forward-only via an opaque cursor, and the known collection ids are a partial non-exhaustive list. It does not describe the item shape or error behavior, but the pagination and partiality disclosures are meaningful.

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?

The description is front-loaded and appropriately short. The first two sentences are somewhat redundant ('Get one page' / 'Returns one page'), but the remaining content about cursor pagination and the partial collection-id list is useful.

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 simple read-only collection tool with no output schema and no annotations, the description covers pagination, collection id scope, and the lack of discovery. It stops short of describing the returned item fields, which would be helpful in the absence of an output schema.

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 schema already documents all three parameters. The description adds friendly collection examples and reinforces the cursor's next_cursor source, but this largely restates schema information; baseline 3 is appropriate.

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?

The description uses a specific verb and resource ('Get one page of a curated Xbox collection') and supplies concrete examples of the collections available. This clearly differentiates it from generic search or game-detail siblings like xbox_search or xbox_game.

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?

It explains pagination via next_cursor and notes there is no discovery endpoint for the full set. However, it does not explicitly say when to use this tool versus xbox_search, xbox_browse, or xbox_game, leaving that inference to the agent.

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