Crawlora MCP

xbox_collection

Read-only

Fetch one cursor-paginated page from a named editorial Xbox collection such as Top Free Games or Xbox Play Anywhere. Use xbox_browse or xbox_search to discover items, or xbox_game for one title.

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>",
      "Cursor": "<Cursor>",
      "Locale": "<Locale>"
    },
    "name": "xbox_collection"
  }
}

Input Schema

Name	Required	Description
`ID`	Yes	Curated collection to fetch. Allowed values: TopFreeGames, TopPaidGames, OptimizedSeriesXS, XboxPlayAnywhere.
`Cursor`	Yes	Opaque pagination cursor from a previous response's next_cursor. Omit for the first page.
`Locale`	Yes	Display locale (BCP-47), default en-US.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 5, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds that each call returns a single paginated page, which is useful, but it says nothing about error behavior, empty collections, or cursor expiry. Adds some value over annotations, hence a 3.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences: the pagination/scoping fact is front-loaded, then the alternative tools. No filler or restatement of the tool name.

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?

An output schema exists and annotations carry the safety profile, so the description needn't explain return values. It is complete for routing and pagination semantics, though it omits any note on cursor reuse or collection availability, leaving minor gaps.

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 description coverage is 100% and it documents ID allowed values, Cursor origin, and Locale default, so the schema does the heavy lifting. The description echoes collection examples already present in the schema and adds no new syntax or format detail. Baseline 3 applies.

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 (Fetch), resource (a named editorial Xbox collection), and scope (one cursor-paginated page), with concrete examples like Top Free Games. An agent can distinguish it from xbox_browse/xbox_search without opening other schemas.

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 the agent to alternatives: xbox_browse/xbox_search for discovery and xbox_game for a single title. It gives clear when-to-use-else guidance but no explicit exclusions or prerequisites (e.g., when a collection fetch is unnecessary).

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

All Crawlora MCP tools Inspect

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

Need Help?