Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

microsoftstore_editorial

Fetch a Microsoft Store editorial article by its ID, typically for product award writeups. Use the editorial_id from a product's award field.

Instructions

Get a Microsoft Store editorial article by id. Returns a Microsoft Store editorial article (currently only seen in the wild as a per-product Microsoft Store Awards writeup). There is no discovery endpoint for editorial ids: they are only found embedded in a product's own award.editorial_id field, returned by /microsoftstore/search, /microsoftstore/category, /microsoftstore/charts, /microsoftstore/publisher, and /microsoftstore/related when that product carries an award. An unknown/invalid id returns a 503 upstream error, not a clean 404 -- the upstream itself does not distinguish the two.

Input Schema

NameRequiredDescriptionDefault
localeNoDisplay locale (BCP-47)
countryNoStore country/region code (ISO-2)
editorial_idYesEditorial content id, from a product's award.editorial_id field

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.4/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 burden and delivers a high-value edge-case disclosure: an unknown/invalid id returns a 503 upstream error rather than a clean 404. It omits auth/rate-limit and locale/country behavior, but the error-semantics warning is exactly the kind of non-obvious behavior an agent needs.

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?

Front-loaded with the core purpose, then layered with provenance and error behavior. Every sentence carries distinct, actionable information with no padding.

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?

No output schema exists, and the description names what is returned and where the id comes from, which is the critical context for a by-id detail endpoint with no discovery path. It does not describe the article's return structure in detail, a minor gap.

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 coverage is 100%, so the schema already documents all three parameters including that editorial_id comes from a product's award.editorial_id field. The description largely restates that provenance and adds nothing on locale or country, so the baseline 3 applies.

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 and resource ('Get a Microsoft Store editorial article by id') and immediately scopes it by noting it is 'currently only seen in the wild as a per-product Microsoft Store Awards writeup.' An agent knows exactly what this returns and can distinguish it from product/search/chart siblings.

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?

Explicitly states there is no discovery endpoint and that ids are only obtainable from a product's award.editorial_id field, naming the five sibling endpoints that surface it. This is precise precondition guidance that tells the agent both when to call it and how to obtain the required input.

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