Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

microsoftstore_spotlight

Fetch curated Microsoft Store home, apps, or games featured hero banners by locale and country; excludes ranked charts and special events.

Instructions

Get the Microsoft Store home page or department spotlight. Returns the curated hero/spotlight shelf shown at the top of the store's home page or one department's landing page (the large featured banners, not the ranked charts or the smaller "Special events" shelf). Only home, apps, and games have a spotlight; any other media_type is rejected.

Input Schema

NameRequiredDescriptionDefault
localeNoDisplay locale (BCP-47)
countryNoStore country/region code (ISO-2)
media_typeNoWhich spotlight to fetch

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.3/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 behavioral burden and does fairly well: it describes the nature of the returned content (curated banners vs. ranked lists), and discloses an input-validation constraint (only home/apps/games accepted, others rejected). It does not describe read-only safety, response shape, or pagination, so a few gaps remain for a zero-annotation tool.

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?

Front-loaded with the core action and return in the first sentence, with constraints following. Three sentences all carry information, though the long parenthetical qualifying which shelf is meant is slightly dense and could be tightened.

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 no-output-schema tool it conveys what the caller gets (hero/spotlight banners) and the valid input domain, which is enough to call it correctly. Missing details about response structure or locale/country fallback behavior keep it from being fully complete.

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 schema already documents locale, country, and the media_type enum, making 3 the baseline. The description adds meaning beyond the schema by explaining what media_type selects (home page vs. department spotlight) and that values outside home/apps/games are rejected, which is useful validation context.

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 first sentence states a specific verb (Get) and resource (Microsoft Store home page or department spotlight), and the second sentence pins down exactly what is returned: the curated hero/spotlight shelf of large featured banners. It explicitly distinguishes itself from the ranked charts and the separate 'Special events' shelf, so an agent can tell it apart from microsoftstore_charts and microsoftstore_events without opening a schema.

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 gives clear selection context: use this for the featured hero shelf, not for ranked charts or the Special events shelf, and it states that only home, apps, and games are valid inputs while other media_type values are rejected. It does not name the alternative tools (e.g. microsoftstore_charts) explicitly, so it stops short of full when-to-use/when-not routing.

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