Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

microsoftstore_events

Access Microsoft Store special-events shelves for apps and games, returning featured limited-time promotional products via the public store API.

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. Credential-free public Microsoft Store data, read directly from the store's own promotional-events API.

Input Schema

TableJSON 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?

With no annotations, the description carries the behavioral disclosure burden. It mentions credential-free public access and that invalid media_type values are rejected, which adds value. However, it doesn't disclose pagination behavior, return format, or error handling beyond the media_type rejection, leaving some gaps.

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?

The description is compact and front-loaded with the core purpose, followed by useful differentiators and constraints. Each sentence contributes value without redundancy, making it well-structured for quick comprehension.

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?

The description provides the purpose, constraints, and authentication context, which is sufficient for an agent to call the tool correctly. It lacks explicit return-value details, but since no output schema existscrazy, this is not required. The only minor gap is lack of pagination details beyond the schema's max page_size.

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 5 parameters with descriptions, achieving 100% coverage. The description adds the domain-specific fact that media_type must be apps or games, which is already enforced by the enum, so it provides minimal extra meaning beyond the schema.

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 description clearly states the tool retrieves a Microsoft Store department's special-events shelf, using a specific verb and resource. It also distinguishes itself from the ranked charts and spotlight siblings, making its purpose unambiguous.

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?

The description explicitly differentiates this tool from /microsoftstore/charts and /microsoftstore/spotlight, telling the agent when to use this over those alternatives. It also states that only apps and games have this shelf, so any other media_type will be rejected, providing clear usage boundaries.

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