Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

microsoftstore_reviews

Fetch paginated Microsoft Store reviews for any product ID with ratings, titles, text, timestamps, votes, and device details. Sort by MostHelpful or MostRecent, and set locale/country.

Instructions

Get paginated Microsoft Store reviews for a product. Returns one page of written Microsoft Store reviews for a product id, each with rating, title, text, submission time, helpful-vote counts, and device/OS info. sort controls ordering (MostHelpful or MostRecent -- the only two values the upstream API itself accepts; any other value is rejected). Credential-free public Microsoft Store data, read directly from the store's own review-listing API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo1-based page number
sortNoReview sort order
localeNoDisplay locale (BCP-47)
countryNoStore country/region code (ISO-2)
page_sizeNoReviews per page (max 50)
product_idYesMicrosoft Store product id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.4/5.0
Behavior4/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 does well: it discloses that only one page is returned, that sort accepts only MostHelpful and MostRecent, that invalid values are rejected, and that the data is credential-free public data read directly from the Microsoft Store API. This gives the agent a clear safety and behavior profile.

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?

Three sentences, each with a distinct job: state the operation, list the returned content, and explain the sort constraint plus data source. No filler or redundancy.

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 six-parameter tool with no output schema and no annotations, the description is largely complete: it states required resource, returned fields, sort behavior, and access characteristics. Minor gaps remain around default pagination values and explicit differentiation from the reviews_summary sibling, but the schema covers parameter details.

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 value beyond the schema by explaining that the sort parameter only accepts the two enum values because the upstream API rejects any other value, which helps the agent avoid failed calls.

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 starts with a specific verb and resource: 'Get paginated Microsoft Store reviews for a product.' It further clarifies it returns one page of written reviews with concrete fields, which distinguishes it from a summary or aggregate tool like microsoftstore_reviews_summary.

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?

The description clearly signals when to use this tool: for paginated written reviews of a product ID. It does not explicitly name alternatives or state when not to use it, but the context is clear enough for an agent to select it over sibling review-summary 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