Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

retailmenot_store

Fetch a RetailMeNot store page's coupons, sales, cash-back and in-store offers, plus store details, ratings, similar stores, and FAQs. Use market=ca for Canada.

Instructions

Get a RetailMeNot store's coupons and offers. Returns a store's RetailMeNot page: store details, shopper rating, category, offer counts, every listed coupon, sale, cash-back, and in-store offer (including the offers behind the page's "show more" button), similar stores, and FAQs. Coupon codes are only revealed on RetailMeNot after a click and are not returned. Set market=ca for a RetailMeNot Canada store page.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainYesStore domain or RetailMeNot store URL
marketNous for RetailMeNot, ca for RetailMeNot Canada (stores from /retailmenot/stores with market=ca)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A4.1/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 does well: it discloses exactly what the response contains (all offers including those behind 'show more', similar stores, FAQs) and an important limitation that coupon codes are not returned because they require a click on RetailMeNot. It omits auth/permission or freshness caveats but the key behavioral facts are stated.

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 sentences, front-loaded with the core action and followed by return contents and the market toggle. The return-field enumeration is dense but each item is informative; minimal waste.

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 compensates by enumerating the returned fields and the coupon-code limitation, so an agent knows what it gets back. It is essentially complete for a two-parameter read tool, lacking only minor details like re-fetch/pagination behavior (largely irrelevant for a single store page).

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% and both parameters are already documented in the schema, so the baseline is 3. The description's market guidance (

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?

Specific verb+resource: retrieves a single RetailMeNot store's page of coupons and offers. It clearly distinguishes itself from the plural sibling retailmenot_stores by describing full store-page contents (details, rating, offers, similar stores, FAQs).

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 concrete usage context with 'Set market=ca for a RetailMeNot Canada store page', which tells the agent how to target the Canadian market. It does not explicitly contrast with retailmenot_stores or other siblings, but the detail-vs-list split is inferable from the content description.

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