Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

retailmenot_deal_events

List RetailMeNot seasonal and holiday deal events to get names, slugs, and URLs for deal-event endpoints; takes no parameters.

Instructions

List RetailMeNot seasonal deal events. Lists the seasonal and holiday deal events linked from RetailMeNot's deals hub, such as Black Friday or Back-to-School, each with name, slug and url. The slug feeds the deal-event endpoint. Out-of-season events may list fewer offers. It takes no parameters.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A4.4/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 meaningful work: it declares the operation takes no parameters, names the returned fields (name, slug, url), and discloses a real data caveat that out-of-season events may list fewer offers. It omits pagination, rate limits and auth expectations, so it is not exhaustive.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences, each carrying distinct information — purpose, return fields, downstream chaining, data caveat. Nothing is redundant and the core purpose is front-loaded.

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?

Since no output schema exists, the description usefully enumerates the returned fields and adds the seasonal-availability caveat plus the downstream slug linkage, which is enough to call and chain the tool correctly. Only pagination/response-size behavior is left unstated.

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, so the baseline is 4. The description confirms this explicitly ('It takes no parameters'), which is consistent with the empty schema and leaves no ambiguity about whether arguments are expected.

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 seasonal deal events') and grounds it with concrete examples (Black Friday, Back-to-School). It distinguishes itself from the singular sibling retailmenot_deal_event by explaining that the returned `slug` 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 Guidelines4/5

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

Explains the context clearly: this is the deals-hub listing, and its `slug` output is the input for the deal-event endpoint, which implicitly routes the agent to the sibling for per-event detail. There is no explicit when-not-to-use statement or exclusion, so it stops short of a 5.

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