Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

slickdeals_deal

Retrieve full detail of a Slickdeals deal thread, including price, votes, comments, expiration, and merchant link, by providing its URL or numeric thread ID.

Instructions

Get one Slickdeals deal thread's full detail. Returns one Slickdeals deal thread's full detail: title, store, final/list price, community vote score, comment count, whether the deal is marked expired, the deal's product category and taxonomy (category/sub_category/category_paths, and separately the legacy forum/forum_id the thread was posted under), the public Slickdeals username who posted it ("found by" attribution) with a public community-standing summary (reputation, join date, deals posted, total votes/comments), a related_deals sidebar (Slickdeals' own Popular/Trending picks), the outbound merchant link, and the deal's own description. Give either url (the exact value returned by GET /slickdeals/search) or thread_id (Slickdeals' own numeric thread id, e.g. from a deal's URL path /f/{thread_id}-...); at least one is required. An unknown or removed deal returns 404.

Input Schema

NameRequiredDescriptionDefault
urlNoFull Slickdeals deal URL, as returned by GET /slickdeals/search (https://slickdeals.net/f/...)
thread_idNoSlickdeals numeric thread id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.1/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 behavioral burden and does well: it specifies the complete return payload (title, prices, vote score, taxonomy, poster standing, related_deals, merchant link) and discloses error behavior on unknown/removed deals ('returns 404'). It could still note read-only safety or rate limits, so not 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.

Conciseness4/5

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

Purpose is front-loaded in a short first sentence, and parameter/error guidance is clean. The middle sentence is a very long run-on enumeration of return fields; it earns space given the absent output schema but could be broken up for readability.

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?

There is no output schema and no annotations, so the description must carry returns and behavior - it does both exhaustively, plus input sourcing and the 404 case. Nothing an agent needs to call this single-item detail tool correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/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 exceeds it: it explains the provenance of url (from GET /slickdeals/search), the format of thread_id (from the /f/{thread_id}-... URL path), and adds the 'at least one is required' constraint that the empty required array in the schema does not convey.

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 opening sentence gives a specific verb and resource: 'Get one Slickdeals deal thread's full detail.' The word 'one' distinguishes it from the sibling search/list tools, and the following enumeration reinforces scope. It stops short of naming a sibling like slickdeals_search or slickdeals_comments, so a 5 isn't warranted.

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?

Usage is implied rather than stated: url is described as 'the exact value returned by GET /slickdeals/search', which hints at a search-then-detail workflow. However there is no explicit guidance on when to pick this over slickdeals_comments or the search tools, and no when-not conditions beyond the 404 note.

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