Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

microsoftstore_search

Search Microsoft Store listings for apps, games, devices, and more by keyword, then filter by department, category, price, or age and paginate through results.

Instructions

Search the Microsoft Store. Returns a page of Microsoft Store search results (apps, games, devices, and other listings) for a keyword, with cursor-based pagination and per-item publisher, rating, price, and media. media_type selects the department (apps, games, devices, passes, fonts, themes, tencent-android, tencent-mini, or all); category further filters within that department (the accepted set depends on media_type -- see the markdown doc for the full per-department lists). Pass the previous response's next_cursor to fetch the next page.

Input Schema

NameRequiredDescriptionDefault
ageNoMaximum-age filter
priceNoPrice filter
queryYesSearch keyword
cursorNoOpaque pagination cursor from a previous response's next_cursor
localeNoDisplay locale (BCP-47)
countryNoStore country/region code (ISO-2)
categoryNoCategory to filter by (accepted set depends on media_type)
media_typeNoDepartment to search

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the burden and usefully states that results are paginated and include publisher, rating, price, and media. It does not cover auth, rate limits, or error behavior, but for a read-only search operation it adds solid behavioral context.

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?

The description is front-loaded with purpose and return shape, then filters and pagination. Every sentence adds useful information without redundant prose.

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?

There is no output schema, but the description explains pagination and the per-item fields returned. With all eight parameters documented in the schema, the definition gives an agent enough to call the tool correctly.

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 meaningful semantics: media_type selects the department, category narrows within that department with an accepted set that depends on media_type, and cursor uses the previous response's next_cursor.

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?

The description opens with a specific verb and resource ("Search the Microsoft Store") and scopes it to keyword search results across apps, games, devices, and other listings. It is clear, but it does not explicitly distinguish itself from Microsoft Store sibling tools such as category, product, or charts endpoints.

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?

It explains that media_type selects the department and category filters within it, and instructs passing the previous response's next_cursor for pagination. However, it gives no explicit when-to-use/when-not guidance or names alternatives among the many Microsoft Store sibling tools.

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