Crawlora MCP

microsoftstore_category

Read-only

Browse one paginated Microsoft Store category without a keyword. Use microsoftstore_search for query-based results.

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": {
      "Category": "<Category>",
      "MediaType": "<MediaType>",
      "Cursor": "<Cursor>",
      "Country": "<Country>",
      "Locale": "<Locale>"
    },
    "name": "microsoftstore_category"
  }
}

Input Schema

Name	Required	Description
`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.
`Country`	Yes	Store country/region code (ISO-2), default US.
`Category`	Yes	Category to browse (the accepted set depends on media_type -- see the search endpoint's docs for the full per-department lists).
`MediaType`	Yes	Department to browse, default apps. Allowed values: apps, games, devices, passes, fonts, themes, tencent-android, tencent-mini (all is not accepted here -- it has no category filter upstream).

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.1/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 results are paginated, which is mildly useful behavioral context, but says nothing about rate limits, result volume, or auth needs beyond what the schema and annotations already imply.

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 short sentences with zero waste. The core scoping constraint ('without a keyword') is front-loaded and the alternative follows immediately.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists so return values need not be explained, and the schema fully documents all required parameters. The description supplies the essential routing information for a browse-by-category tool, so nothing an agent needs in order to call it correctly is missing.

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%, so all five parameters (Category, MediaType, Cursor, Country, Locale) are already documented in the schema, including MediaType's allowed values and Cursor's opaque pagination semantics. The description adds no parameter-level detail, so baseline 3 is correct.

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 ('Browse') and resource ('one paginated Microsoft Store category'), and explicitly distinguishes itself from microsoftstore_search ('without a keyword'). An agent can tell it apart from the search sibling without opening either schema.

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?

Gives clear context ('browse one category without a keyword') and names an explicit alternative ('Use microsoftstore_search for query-based results'). It does not address when to prefer other siblings like microsoftstore_categories, charts, editorial, or spotlight, so it falls just short of full when/when-not coverage.

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?