Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

retailmenot_home

Fetches RetailMeNot homepage offers, including cash-back rates, seasonal deals, top product discounts, and help FAQ.

Instructions

Get RetailMeNot's homepage offers. Returns RetailMeNot's homepage: featured offer sections (cash-back stores with rates, seasonal savings deals with store, offer type, discount, and title), today's top product deals (title, discount, image, and retailer product URL), and the help FAQ.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations and no output schema, the description carries the full burden and does well: it discloses the returned content groups and their fields (cash-back rates, deal store/type/discount/title, product deal title/discount/image/URL, FAQ). It omits auth, rate-limit, and freshness/caching behavior, preventing a 5.

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?

A single dense sentence that leads with the purpose and then lists the payload contents. It is front-loaded and waste-free, though the nested enumeration of fields makes it slightly long rather than crisp.

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?

For a zero-parameter, no-annotation, no-output-schema tool, the description substitutes for the missing return documentation by enumerating what comes back. An agent can call it correctly with no further information; only peripheral details like auth or data freshness are absent.

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?

The tool takes zero parameters, so there is nothing to document; the baseline for a no-param tool is 4. The description correctly focuses on return content instead of inventing parameter semantics.

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 ('Get RetailMeNot's homepage offers') and immediately enumerates the three content groups the page contains. It is clearly a homepage/browse endpoint, distinguishable from the many retailmenot_* siblings, though it never explicitly contrasts itself with them (e.g. retailmenot_store, retailmenot_cashback).

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?

Usage is only implied: the tool takes no arguments and fetches a fixed homepage, so 'when to use' is largely self-evident. There is no explicit statement of when to prefer this over retailmenot_stores or retailmenot_categories, and no prerequisites are given.

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