Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

retailmenot_cashback

List RetailMeNot cash-back offers by section, showing store, URL, and cash-back rate; no input parameters required.

Instructions

List RetailMeNot cash-back offers. Lists the offers on RetailMeNot's cash-back page, grouped into sections such as Today's Featured Cash Back, Top Cash Back and All Cash Back Offers. Each offer has its position, store name, domain and RetailMeNot URL, the cash-back rate in discount, and a title. It takes no parameters.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are present, so the description carries the behavioral burden. It helpfully states that the tool takes no parameters and describes the returned offer fields, but it does not mention pagination, authorization requirements, rate limits, or other operational details.

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?

The description is short and front-loaded with the core purpose. It has minor redundancy between 'List RetailMeNot cash-back offers' and 'Lists the offers on RetailMeNot's cash-back page,' but the remaining sentences efficiently describe grouping and item fields.

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, the description compensates by listing the returned fields (position, store name, domain, URL, discount, title) and section structure. For a no-parameter listing tool, this is reasonably complete, though pagination and rate-limit context 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 has zero parameters and the description explicitly says 'It takes no parameters,' so there is no parameter semantics gap. Baseline for zero-param tools applies.

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 and resource: 'List RetailMeNot cash-back offers.' It clearly identifies the cash-back page as the source and is distinguishable from general RetailMeNot store/category tools, though it does not explicitly contrast itself with siblings like retailmenot_deal_events or retailmenot_stores.

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 implied by the resource focus: use it to see cash-back offers grouped on RetailMeNot's cash-back page. However, it gives no explicit when-to-use/when-not guidance or names an alternative sibling for related tasks.

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