Crawlora MCP

xbox_reviews

Read-only

A product's aggregate star-rating breakdown and written reviews, optionally sorted (most helpful/most recent) and/or filtered to one exact star rating.

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": {
      "ProductID": "<ProductID>",
      "ItemCount": "<ItemCount>",
      "OrderBy": "<OrderBy>",
      "StarFilter": "<StarFilter>",
      "Locale": "<Locale>"
    },
    "name": "xbox_reviews"
  }
}

Input Schema

Name	Required	Description
`Locale`	Yes	Display locale (BCP-47), default en-US.
`OrderBy`	Yes	Review sort order, default MostHelpful. Allowed values: MostHelpful, MostRecent.
`ItemCount`	Yes	Number of reviews to return (1-25), default 10.
`ProductID`	Yes	Xbox catalog product id.
`StarFilter`	Yes	Only return reviews with this exact star rating (1-5). Omit for all ratings.

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

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds that the response contains both an aggregate rating breakdown and written reviews, which is useful output context, but it says nothing about pagination limits, locale-dependent behavior, or empty-result handling.

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?

A single front-loaded sentence that names the resource first, then the optional modifiers, with zero filler or repetition.

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?

With an output schema present, the description need not explain return values, and the annotations carry the read-only/open-world profile. Only marginal gaps remain: no note on whether reviews are paginated beyond ItemCount or what happens when the product has no reviews.

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%, covering ProductID, ItemCount range, OrderBy values, StarFilter meaning, and Locale format. The description's mention of sorting and star filtering mirrors the schema without adding syntax or edge-case detail, so the baseline 3 applies.

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?

States a specific resource and content type — a product's aggregate star-rating breakdown plus written reviews — which is unambiguous versus siblings like xbox_game or xbox_search. It never names those siblings explicitly, so differentiation is inferable rather than stated, keeping it below 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The sentence describes what can be optionally sorted or filtered, but never states when to reach for this tool versus xbox_game (details) or xbox_search (discovery). Usage is only implied by the resource name, with no exclusions or prerequisites.

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?