Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

xbox_search

Search the Xbox catalog by keyword, then filter or sort games, add-ons, and hardware. Returns one cursor-paginated page of matching results.

Instructions

Search the Xbox catalog, with optional sort and filters. Returns one page of Xbox search results for a keyword, scoped to a category (games, add-ons, or hardware) and optionally sorted/filtered with the same parameters as /xbox/browse. Cursor-paginated.

Input Schema

NameRequiredDescriptionDefault
sortNoSort order
genreNoGenre filter (repeatable)
priceNoPrice-band filter (repeatable)
queryYesSearch keyword
cursorNoOpaque pagination cursor from a previous response's next_cursor
localeNoDisplay locale (BCP-47)
categoryNoResult category
platformNoPlatform filter (repeatable)
age_ratingNoESRB age-rating filter (repeatable)
multiplayerNoMultiplayer-mode filter (repeatable)
subscriptionNoSubscription filter, by the subscription's own product id (repeatable)
accessibilityNoAccessibility-feature filter (repeatable)
supported_languageNoSupported-language filter, by BCP-47 tag (repeatable)
technical_featuresNoTechnical-feature filter (repeatable)
handheld_compatibilityNoHandheld compatibility filter (repeatable)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It usefully discloses that it returns a single page and is cursor-paginated, which is genuine behavioral context. It does not mention permissions, rate limits, or result richness, leaving significant gaps for a 15-param tool.

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 verb and resource, and the two sentences are tight with no filler. The pagination note at the end is functional rather than ornamental.

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 search tool with 15 fully-documented params and no output schema, the description covers return scope, pagination, and category filtering adequately. It could do slightly more to route versus xbox_browse, but an agent has enough to invoke it correctly.

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 documents all 15 parameters including the category enum. The description adds marginal value by restating the category options (games, add-ons, hardware) and noting sort/filter parity with /xbox/browse, but does not explain semantics beyond the schema. Baseline 3 is appropriate.

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 clear verb+resource ("Search the Xbox catalog") and specifies what it returns ("one page of Xbox search results for a keyword"). It scopes the resource to a category and mentions relations to /xbox/browse, but does not explicitly distinguish itself from the sibling xbox_browse tool, so full sibling differentiation is missing.

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?

Usage is implied: it searches "for a keyword" which suggests use when a query term exists, and it references similarity to /xbox/browse. However, there is no explicit when-to-use vs alternatives routing or exclusion (e.g., use xbox_browse when you have no keyword).

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