Crawlora MCP

slickdeals_search_advanced

Read-only

Search Slickdeals with real pagination, integer vote/comment/view counts, and facets (Categories/Stores/Brands with id+count) -- a richer alternative to slickdeals_search's keyword-only RSS feed. category_id/brand_id/store_id are passthrough filters sourced from a prior response's own facets, not a validated closed enum.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "q": "<q>"
    },
    "name": "slickdeals_search_advanced"
  }
}

Input Schema

Name	Required	Description
`q`	Yes	Free-text keyword query
`page`	No	1-based result page, default 1
`sort`	No	Sort order, default relevance
`brand_id`	No	Brand facet id, from a prior response's own facets
`store_id`	No	Store facet id, from a prior response's own facets
`category_id`	No	Category facet id, from a prior response's own facets

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 7, 2026
- addedInput schema / properties / brand_id / description
```
Added value: +"Brand facet id, from a prior response's own facets"
```
- addedInput schema / properties / category_id / description
```
Added value: +"Category facet id, from a prior response's own facets"
```
- addedInput schema / properties / page / description
```
Added value: +"1-based result page, default 1"
```
- addedInput schema / properties / q / description
```
Added value: +"Free-text keyword query"
```
- addedInput schema / properties / sort / description
```
Added value: +"Sort order, default relevance"
```
- addedInput schema / properties / store_id / description
```
Added value: +"Store facet id, from a prior response's own facets"
```
First observedOct 5, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, but the description adds real value beyond them: it discloses that the facet filters are passthrough (not a validated closed enum) and that they are sourced from a prior response's own facets. This is a genuine behavioral trait that affects correct invocation and prevents the agent from inventing arbitrary ids.

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?

Two sentences with the core capability front-loaded and zero filler. It is dense and packs a lot of distinctions into a small space, but every clause (pagination, integer counts, facets, the sibling comparison, the passthrough warning) 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 an output schema present, the description need not explain return values, and safety is covered by annotations; it still usefully names the returned counts and facets and clarifies the passthrough filter semantics. Combined with full schema coverage and clear sibling routing, an agent has what it needs to call the tool 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 is 3, but the description adds meaning: it clarifies that category_id/brand_id/store_id are passthrough filters whose values must come from a prior response's own facets and are not a validated closed enum. This resolves the ambiguity of where valid ids originate, going beyond the schema's field-level descriptions.

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 (Search Slickdeals) and immediately differentiates via concrete capabilities: real pagination, integer vote/comment/view counts, and id+count facets. It names the sibling it improves upon (slickdeals_search) and characterizes that sibling as a keyword-only RSS feed, so an agent can distinguish the two without opening either schema.

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?

The description explicitly routes the agent by calling itself 'a richer alternative to slickdeals_search's keyword-only RSS feed,' giving clear context for when this tool beats the sibling. It stops short of stating explicit when-not conditions or listing further alternatives, so guidance is clear but not fully spelled out.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?