Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

microsoftstore_product

Fetch Microsoft Store listing details for a product ID, including title, pricing, ratings, platforms, media, and version data. Use locale and country to get region-specific store data.

Instructions

Get Microsoft Store details for a single product. Returns Microsoft Store listing details for a single product id: title, description, publisher, category, media type, aggregate rating and content-rating breakdown, price and SKU summary, size, supported platforms/languages, capabilities, version/release/update timestamps, feature callouts, and media (icon, poster art, screenshots, trailers).

Input Schema

NameRequiredDescriptionDefault
localeNoDisplay locale (BCP-47)
countryNoStore country/region code (ISO-2)
product_idYesMicrosoft Store product id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.5/5.0
Behavior3/5

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

No annotations exist, so the description carries the full behavioral burden. It helpfully enumerates the returned payload (ratings, pricing, SKU, media, timestamps), which is real value since there is no output schema, but it discloses nothing about auth requirements, rate limits, error behavior, or locale/country fallback.

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 sentence, with the field inventory following. The second sentence is a long comma list but every element is a distinct returned attribute, so it is dense rather than wasteful.

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?

With no output schema, the description compensates by enumerating return fields, and all three parameters are documented. It is nearly complete for a detail-fetch tool; the only gap is the absence of any annotation-substitute context such as auth or error handling.

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 the schema already documents product_id, locale (BCP-47), and country (ISO-2). The description adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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 ('Get') and resource ('Microsoft Store details for a single product'), scoped to a product id. This distinguishes it functionally from siblings like microsoftstore_search or microsoftstore_related, though it never names an alternative explicitly.

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 only implied: 'for a single product id' signals the tool needs an already-known id rather than a query, which separates it from search/suggest. There is no explicit when-to-use statement, no when-not-to-use, and no named sibling alternative.

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