Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

microsoftstore_category

Browse a Microsoft Store category without a search keyword. Returns cursor-paginated department listings, so you can list an entire category when keyword search is not possible.

Instructions

Browse a Microsoft Store category without a keyword. Returns a page of a single department+category listing, cursor-paginated, with no search keyword required -- the way to list an entire category (search requires a non-empty query and returns nothing for an empty one). category is required; the accepted set depends on media_type (see /microsoftstore/search's markdown doc for the full per-department lists). media_type defaults to apps; all is not accepted here since it has no category filter.

Input Schema

NameRequiredDescriptionDefault
cursorNoOpaque pagination cursor from a previous response's next_cursor
localeNoDisplay locale (BCP-47)
countryNoStore country/region code (ISO-2)
categoryYesCategory to browse
media_typeNoDepartment to browse

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.3/5.0
Behavior4/5

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

No annotations are provided, so the description carries full burden, and it does disclose real behavior: it returns one page of a department+category listing, is cursor-paginated, and takes no keyword. It omits permissions/rate/auth context, but for a browse operation the pagination and return-shape disclosure is solid.

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?

Purpose is front-loaded in the first clause and the search contrast follows logically. It is somewhat dense with parentheticals, but each clause conveys a distinct constraint rather than restating structured data.

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?

No output schema exists, and the description explains the return nature (a paginated department+category page) so the agent knows what to expect. It defers the full per-department category lists to another tool's markdown doc, which is an acknowledged external dependency rather than an inline answer.

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 baseline is 3, but the description adds meaning: category is required, the accepted set depends on media_type, media_type defaults to apps, and 'all' is not accepted here. The default-value and enum-exclusion notes go beyond the schema.

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+resource ('Browse a Microsoft Store category') and the exact scope (a single department+category listing page), and explicitly contrasts it with search, which the agent could otherwise confuse it with. An agent can distinguish this from microsoftstore/search 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?

Clearly says when to use it ('the way to list an entire category') and when not (search requires a non-empty query and returns nothing for an empty one), plus the media_type default and the 'all' exclusion. It does not clarify its relationship to the sibling microsoftstore_categories (the category index), leaving one alternative unnamed.

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