Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

retailmenot_category

Fetch RetailMeNot category offers by slug, returning paginated featured store deals, offer counts, and similar stores.

Instructions

Get a RetailMeNot category's offers. Returns one page of a RetailMeNot category landing page: the featured offers across stores (24 per page, with page and total_pages), offer counts, and similar stores. Use a slug from /retailmenot/categories; a page past the end returns an empty offer list.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoOffer page (24 offers per page; see total_pages)
slugYesCategory slug from /retailmenot/categories

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, the description carries the full burden and does well: it discloses the pagination model (24 per page, page and total_pages), the payload composition (featured offers, offer counts, similar stores), and the edge-case behavior that a page past the end returns an empty offer list. It omits auth/rate-limit context, keeping it short of 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.

Conciseness5/5

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

Three front-loaded sentences with no filler: purpose first, return shape second, input sourcing and edge case last. Every sentence earns its place.

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 and no annotations, the description compensates by describing the return payload and pagination behavior, which is what an agent needs to call and interpret results correctly. Auth and rate-limit details are the only notable omissions.

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%, so the schema already documents both params, giving a baseline of 3. The description reinforces the slug source and adds page-past-end behavior, but adds only marginal meaning beyond what the schema already conveys.

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?

The description opens with a specific verb+resource: 'Get a RetailMeNot category's offers,' and clarifies it returns a category landing page, distinguishing it from a store-offers shape. It does not explicitly name siblings like retailmenot_store or retailmenot_categories, but the scope is clear enough for an agent to select it.

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 tells the agent where to source the required slug ('Use a slug from /retailmenot/categories'), which is useful input guidance. However, it offers no when-to-use vs. when-not guidance, nor any comparison to sibling tools such as retailmenot_store or retailmenot_categories.

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