Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

microsoftstore_publisher

Retrieve every Microsoft Store product listed by a publisher or developer using an exact publisher name, with cursor-based pagination for complete catalogs.

Instructions

List a Microsoft Store publisher's full catalog. Returns every product a publisher/developer has listed on the Microsoft Store, cursor-paginated. publisher_name must match the publisher name exactly as shown on a listing (e.g. the publisher field returned by /microsoftstore/product or /microsoftstore/search).

Input Schema

NameRequiredDescriptionDefault
cursorNoOpaque pagination cursor from a previous response's next_cursor
localeNoDisplay locale (BCP-47)
countryNoStore country/region code (ISO-2)
publisher_nameYesExact publisher/developer name

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that the result is the complete catalog and is cursor-paginated, but says nothing about ordering, page-size limits, permission/auth requirements, or empty-result behavior for an unbounded list.

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?

Three front-loaded sentences with no filler: purpose, return shape/pagination, then input constraint. The only minor redundancy is restating "full catalog" and "every product," but overall it is tight and well-structured.

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?

With no output schema and no annotations, the description covers what is returned (all of a publisher's products) and how to page through it, which is the key missing context. It omits details such as returned fields and default page size, keeping it short of 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 baseline is 3. The description adds real operational meaning for the required field: publisher_name must match exactly as shown on a listing and can be obtained from the product/search endpoints — guidance the schema's bare "Exact publisher/developer name" does not convey.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ("List a Microsoft Store publisher's full catalog") and scopes it to every product a publisher has listed, which separates it from catalog/product-oriented siblings like microsoftstore_product or microsoftstore_search. It does not explicitly name those siblings as alternatives, so it lands just short of 5.

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?

Gives clear context for when the tool applies (enumerating a whole publisher/developer catalog) and, importantly, tells the agent how to source the required argument from microsoftstore_product or microsoftstore_search. It offers no explicit when-not-to-use or alternative-selection guidance.

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