Skip to main content
Glama

PostThisDeal Handpicked Deals

Search PostThisDeal handpicked deals

search_deals
Read-onlyIdempotent

Search the live deals PostThisDeal's team has handpicked (only published posts; ended, expired and unavailable deals are left out). Filter by words, retailer, brand, category, price range, minimum discount (only deals whose discount is backed by two stated prices) and online or in-store availability; sort by relevance, newest, price, discount or most recently checked. Ranking uses relevance, price and freshness only, never commission. Each deal has links.source_url (the PostThisDeal page to credit) and links.purchase_url (the shopping link: present it unchanged as the purchase action) plus a disclosure. An empty result means nothing matched.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_deals"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNo
brandNo
limitNo
queryNoWords that would appear in a deal title, e.g. "canon camera", "tv".
cursorNonext_cursor from the previous page.
categoryNoe.g. "electronics", "home-kitchen", "grocery".
retailerNoShop name, e.g. "Walmart", "Amazon".
max_priceNo
min_priceNo
availabilityNoany
min_discountNo
recently_checkedNoOnly deals whose price a check at the merchant confirmed within its freshness window.

Output Schema

NameRequiredDescriptionDefault
noteNo
dealsYes
returnedYes
next_cursorYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / deals / items / properties / links / properties / record_url
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
  2. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the readOnly/idempotent/closed-world annotations, the description discloses ranking policy ('relevance, price and freshness only, never commission'), a data-quality guarantee for discounts ('backed by two stated prices'), the semantics of recently_checked, and the credit/purchase link contract. It also states what is excluded from the result set, which annotations cannot convey.

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?

Purpose and corpus scope lead, followed by filter/sort capability, then ranking policy, then link handling and the empty-result note. Dense but every clause carries operational information; nothing is redundant with the schema or annotations.

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?

For a 12-parameter search tool with an output schema, the definition covers inclusion rules, ranking rationale, link fields, and empty results. The one gap is pagination mechanics (limit/cursor), which an agent needs to page correctly and which neither the description nor the schema fully spells out.

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?

With schema coverage at 42%, the description compensates well: it explains min_discount's two-price backing, availability as online vs in-store, the sort dimensions, and the filter families (words, retailer, brand, category, price range). It says nothing about limit or cursor paging behavior, which the schema only partially documents.

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?

States a specific verb and resource ('Search the live deals PostThisDeal's team has handpicked') and immediately bounds the corpus to published posts, excluding ended/expired/unavailable deals. It does not name the sibling tools (get_latest_deals, get_deal), but the enumerated filter and sort surface makes the search-oriented role distinguishable.

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?

Gives clear context for when this tool applies: when the agent needs to filter by words, retailer, brand, category, price, discount, or availability, or sort results. It also defines the empty-result case. It stops short of explicit exclusions or naming which sibling to use for a single known deal or for the latest feed.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources