Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

retailmenot_blog_posts

List RetailMeNot blog posts with title, URL, excerpt, author, dates, images, categories, and tags. Filter by category, tag, or search; sort by date, modified, title, or relevance.

Instructions

List RetailMeNot blog posts. Returns one page of RetailMeNot blog posts (title, slug, URL, excerpt, description, author, published and modified dates, image, categories, and tags) with total and total pages, newest first by default. Filter by category slug, tag slug, and/or a search query; order by date, modified, title, or relevance (relevance requires query). A page past the end returns an empty list.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagNoTag slug from /retailmenot/blog-tags
pageNoPage number, starting at 1
orderNoSort direction
queryNoSearch post text
categoryNoCategory slug from /retailmenot/blog-categories
order_byNoSort field
page_sizeNoPosts per page (1-100)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A4.5/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 returned fields, that pagination totals (total and total pages) are included, the default ordering (newest first), the relevance-requires-query constraint, and the edge behavior that a page past the end returns an empty list. It omits auth/rate-limit context but adds substantial behavioral value.

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, each earning its place: purpose, return shape/pagination, then filtering/ordering rules. No filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, so the description appropriately names the returned fields and pagination totals. Combined with 100% parameter coverage and the edge-case note, an agent has everything needed to invoke it correctly.

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?

Schema coverage is 100%, so the baseline would be 3; the description goes beyond the schema by stating the default sort direction (newest first) and the conditional rule that relevance ordering requires a query parameter, which the schema's enum does not express.

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+resource ('List RetailMeNot blog posts') and immediately distinguishes itself from the singular sibling retailmenot_blog_post by noting it returns 'one page' of posts. An agent can tell this is the collection endpoint versus the detail 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?

Clearly explains how to use it: filter by category slug, tag slug, and/or query; order by date, modified, title, or relevance. Includes the constraint that relevance requires a query. It lacks an explicit pointer to siblings (e.g. use retailmenot_blog_post for a single post), but the usage context is otherwise clear.

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