Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

slickdeals_primary_category

Retrieve current deal listings from a Slickdeals featured primary category, including title, price, store, vote score, and comment count.

Instructions

Browse current deals in one Slickdeals featured primary category. Returns the current deal listing for one Slickdeals featured primary-category landing page (e.g. laptop-deals, tv-deals): for each deal, title, price, list price, store, community vote score, comment count, found-by username, and status flags. slug must be one of the values from GET /slickdeals/primary-categories -- an unrecognized slug (including a valid GET /slickdeals/categories tag slug, which is a different taxonomy) returns a typed invalid-parameter error rather than being sent upstream.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesFeatured-category slug from GET /slickdeals/primary-categories

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral disclosure burden. It enumerates the returned deal fields and explains that an unrecognized slug returns a typed invalid-parameter error rather than being sent upstream. It does not cover auth or rate limits, but for a read-only browse operation this is reasonable.

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?

Three dense sentences with the purpose front-loaded; the field list and validation warning each earn their place. There is slight redundancy between 'featured primary category' and 'featured primary-category landing page' that keeps it from a perfect score.

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 enumerates all returned deal fields and explains the input source and error behavior. It does not discuss pagination or deal count, but for a one-parameter read endpoint that is a minor gap.

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 schema already documents slug as 'Featured-category slug from GET /slickdeals/primary-categories', so the baseline is 3. The description adds concrete examples (laptop-deals, tv-deals) and clarifies the boundary with categories slugs, which provides real value beyond the schema.

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 'Browse current deals in one Slickdeals featured primary category' and specifies the resource as a featured primary-category landing page. It also distinguishes its slug taxonomy from GET /slickdeals/categories, which separates it from sibling category tools without needing to inspect their schemas.

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?

Directs the user to obtain the slug from GET /slickdeals/primary-categories and warns that a valid categories tag slug is a different taxonomy that will produce an error. This is clear operational guidance, though it does not explicitly name the alternative tool for tag-category browsing.

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