Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

microsoftstore_reviews

Fetch paginated Microsoft Store reviews for a product by product ID. Return ratings, text, dates, helpful votes, device/OS info; sort by MostHelpful or MostRecent.

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).

Input 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

A3.7/5.0
Behavior4/5

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

With annotations absent the description carries the full burden and does real work: it discloses pagination behavior ('one page'), enumerates the returned fields (rating, title, text, submission time, helpful votes, device/OS), and warns that invalid sort values are rejected by the upstream API. It still omits auth requirements and anything about locale/country defaults, so it is not complete.

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?

Three sentences, front-loaded with purpose and return shape, with no redundant framing. The sort parenthetical is lengthy but earns its place by stating the upstream validation rule, though it is slightly verbose for what the enum already shows.

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 6-parameter, no-output-schema tool, the description adequately covers purpose, pagination, return fields, and sort behavior. Missing locale/country defaulting behavior is a minor gap given the schema documents those parameters.

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 every parameter is already documented, establishing the baseline of 3. The description only elaborates on `sort` (its two accepted values), which the enum already conveys, and adds no new meaning for page, locale, country, or page_size.

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?

States a specific verb and resource ('Get paginated Microsoft Store reviews for a product') with clear scope. It is tellable apart from a generic ratings tool by the emphasis on 'written ... reviews', but it never names the sibling microsoftstore_reviews_summary it overlaps with, so sibling differentiation is only implied.

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?

Usage is implied by the resource it fetches, but there is no explicit when-to-use guidance, no prerequisites, and no routing to alternatives such as the summary/related review tools. An agent must infer the context of use.

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