Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

retailmenot_stores

List every RetailMeNot store for a chosen directory letter and market, returning the domain needed to query that store's details.

Instructions

List RetailMeNot stores by letter. Returns every store in one letter of RetailMeNot's A-Z store directory, or of RetailMeNot Canada's store list with market=ca, with the domain to pass to /retailmenot/store (with the same market).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
letterYesDirectory letter
marketNous for RetailMeNot, ca for RetailMeNot Canada

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A3.9/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 discloses the return scope ('every store in one letter') and the inclusion of a follow-up domain, which is useful, but says nothing about pagination, result size, ordering, or whether the listing is a full crawl versus a capped page.

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?

One dense sentence with the core action front-loaded and no filler. It is slightly run-on once the downstream endpoint clause is appended, but every clause conveys actionable information.

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 annotations and no output schema, the description still conveys what the call returns and how the output connects to the sibling store endpoint. It stops short of describing the shape of each returned store entry, but is otherwise sufficient for a two-parameter listing tool.

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% with enum descriptions, so the baseline is 3. The description adds genuine value beyond the schema by tying market to a distinct store list (Canada) and by clarifying that the returned domain should be paired with the same market when calling /retailmenot/store.

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 ('List RetailMeNot stores by letter') and scopes it precisely to one letter of the A-Z directory. It also implicitly separates itself from the singular retailmenot_store sibling by noting the returned domain feeds that endpoint.

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

Usage Guidelines3/5

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

The description explains the market parameter's effect (market=ca switches to the Canada list) and points at the downstream /retailmenot/store call, which implies when the output is useful. However, it never states when to use this browsable directory versus a targeted store lookup or search, so usage is only implied.

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