Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

microsoftstore_events

Fetch a Microsoft Store department's special-events shelf to see featured and limited-time apps or games, excluding ranked charts and spotlight listings.

Instructions

Get a Microsoft Store department's special-events shelf. Returns a department's "Special events" promotional shelf -- featured/limited-time products, distinct from the ranked charts (/microsoftstore/charts) and the curated home/department spotlight (/microsoftstore/spotlight). Only apps and games have this shelf; any other media_type is rejected.

Input Schema

NameRequiredDescriptionDefault
pageNo1-based page number
localeNoDisplay locale (BCP-47)
countryNoStore country/region code (ISO-2)
page_sizeNoItems per page (max 24)
media_typeNoDepartment to fetch special events for

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It usefully discloses the failure mode (media_type other than apps/games is rejected) and the nature of the returned content (featured/limited-time), but says nothing about pagination behavior, auth/permission needs, or return shape for a read endpoint.

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?

Two tight sentences, with the core purpose and the sibling distinctions front-loaded and the media_type constraint closing it out. No filler.

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 read-only list tool with no output schema and full schema coverage, the description covers purpose, sibling routing, and the key input constraint. It stops short of any pagination/return-format note, but nothing essential to correct invocation is missing.

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 all five parameters including the media_type enum. The description reinforces that media_type selects the department and that non-apps/games values are rejected, but adds no syntax beyond the schema. Baseline 3 is appropriate.

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?

States a specific verb+resource (get a department's special-events shelf) and immediately scopes it as a promotional/limited-time shelf. It explicitly names the sibling shelves it is not (charts, spotlight), so an agent can distinguish it without opening schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Names two alternatives (ranked charts at /microsoftstore/charts and curated spotlight at /microsoftstore/spotlight) and the media_type constraint that selects this tool, effectively routing the agent. Nothing about when to prefer this shelf is left to inference.

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