Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

microsoftstore_product

Retrieve comprehensive Microsoft Store product details (title, publisher, rating, price, media, specs) for a single product ID. Returns normalized listing data from the store's public API.

Instructions

Get Microsoft Store details for a single product. Returns normalized 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). Credential-free public Microsoft Store data, read directly from the store's own page-data API.

Input Schema

TableJSON 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

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries full weight. It discloses that the data is credential-free, public, normalized, and sourced from the store's page-data API, which tells an agent that no auth is needed and the output is a transformed representation. It doesn't cover rate limits or error behavior, but the essential read-only/public profile is explicit.

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?

The first sentence front-loads the purpose, and the second sentence is a complete but compact inventory of return fields plus the data source. No filler – every clause adds information, though the list is on the longer side.

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?

Given no output schema, the description's enumeration of returned fields is valuable and largely sufficient. It omits failure behavior and rate limits but tells an agent what to expect and that no credentials are required, which is solid for a single-item read tool.

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?

The input schema already documents all three parameters with descriptions, so the description need not add parameter-level detail. It reinforces that product_id is the key identifier but adds no new semantics beyond the schema, matching the baseline-3 case.

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 verb 'Get' plus the resource 'Microsoft Store details for a single product' make the operation unambiguous. The description names the exact scope (single product id) and enumerates output categories, distinguishing it from sibling list/search/review tools without naming them.

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 makes the use case clear: when you have a product id and want that product's listing details, this is the tool. It doesn't explicitly name alternatives like microsoftstore_search or microsoftstore_reviews, but the single-product focus provides sufficient context.

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