Skip to main content
Glama

PostThisDeal Handpicked Deals

Latest handpicked deals

get_latest_deals
Read-onlyIdempotent

Deals published or updated most recently, newest first, optionally only since a time and for a retailer or category. Ended, expired and unavailable deals are left out unless include_ended is true. 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.

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": "get_latest_deals"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
sinceNoOnly deals published or updated after this time (ISO 8601).
cursorNonext_cursor from the previous page.
categoryNo
retailerNo
include_endedNo

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

A3.8/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, yet the description adds real value beyond them: the newest-first ordering, the default exclusion of ended/expired/unavailable deals, and the instruction to credit links.source_url and present links.purchase_url unchanged as the purchase action. That presentation/attribution rule is genuine behavioral context an output schema would not convey.

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?

Front-loaded with purpose and ordering, then filters, then return-value semantics; every sentence carries information. The final sentence is dense with field-level detail that could be tightened but is not wasted.

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?

Covers ordering, default filtering, the include_ended escape hatch, and the two link fields, which is enough to call the tool correctly against a six-parameter read with an output schema. Pagination via cursor and the maximum limit are only described in the schema, 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?

Schema description coverage is only 33% (since and cursor documented), and the description compensates by explaining the meaning of retailer, category, and include_ended, including the non-obvious default that ended deals are hidden. It says nothing about limit or its 20-item cap, leaving one parameter unexplained in both places.

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 resource and ordering ('Deals published or updated most recently, newest first') so the agent knows exactly what comes back. It never names a sibling, so the boundary with search_deals and get_deal must be inferred from the ordering/freshness framing rather than stated.

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?

Gives condition-level guidance for the parameters ('only since a time and for a retailer or category', 'unless include_ended is true'), which implies when to use each filter. It does not say when to prefer this over search_deals or get_deal for a single deal, so tool selection is left implicit.

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