Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

microsoftstore_charts

Fetch curated Microsoft Store charts (top free, paid, grossing, trending, deals, new releases, most popular), scoped by category, country, locale, media type, and filters.

Instructions

Get a curated Microsoft Store chart. Returns a curated Microsoft Store chart (top free, top paid, top grossing, trending, deals, new releases, getting-started picks, or -- apps only -- most popular), optionally scoped to a category/subcategory and, for games, by Xbox Game Pass availability or player count. Some charts (notably NewAndRising) can legitimately return fewer items than page_size even at the first page -- that reflects real upstream sparsity for that chart, not a parsing gap. Credential-free public Microsoft Store data, read directly from the store's own curated-list API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
listYesChart to fetch
pageNo1-based page number
localeNoDisplay locale (BCP-47)
countryNoStore country/region code (ISO-2)
categoryNoOptional category to scope the chart to further
page_sizeNoItems per page (max 24)
media_typeNoDepartment to scope the chart to
subcategoryNoOptional finer subcategory within category (apps only; requires category to also be set)
discount_filterNoOptional discount filter
num_players_filterNoOptional player-count filter (games only)
subscription_filterNoOptional subscription filter (games only)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.5/5.0
Behavior5/5

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

With no annotations, the description carries the full burden, and it delivers: 'Credential-free public Microsoft Store data, read directly from the store's own curated-list API' states auth and source, and the NewAndRising sparse-results note explains an important non-obvious behavior without attributing it to a parsing bug.

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 dense with useful information, with only minor redundancy between 'Get a curated Microsoft Store chart' and 'Returns a curated Microsoft Store chart.' The edge-case and auth notes are placed appropriately.

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 an 11-parameter tool with no annotations and no output schema, the description covers the main options, auth model, source, and an important pagination anomaly. It does not describe the response shape in detail, but the schema carries the remaining parameter documentation.

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; the description adds value by mapping chart names to scoping/department constraints, including 'apps only' for MostPopular and games-only filters for Game Pass and player count. This cross-parameter guidance exceeds what the individual enum descriptions provide.

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 ('Get') and resource ('curated Microsoft Store chart') and enumerates the exact chart kinds, so its scope is unambiguous. It is clearly distinct from sibling Microsoft Store tools such as microsoftstore_search, microsoftstore_product, and microsoftstore_categories.

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?

It gives concrete usage context: optional category/subcategory scoping, games-only filters for Game Pass and player count, and the apps-only nature of MostPopular. It does not explicitly name alternatives or when-not-to-use conditions, but the intended context is clear.

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