Skip to main content
Glama

There's An AI For That

Search deals

search_deals
Read-only

List or search TAAFT partner deals. Results use the same approved offers as the public deals page and include full tool details plus the TAAFT code, discount, plan, terms, trial, and expiry data when known.

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
sortNobiggest-discount
taskNoOptional task name or task slug.
limitNoOptional result cap. Omit it to list every matching deal.
queryNoOptional keywords such as "social media scheduling".
featureNoOptional feature or tag.
pricing_modelNo
min_discount_amountNo
min_discount_percentNo

Output Schema

NameRequiredDescriptionDefault
dealsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedOutput schema / properties / deals / items / properties / deal / properties / description_trial_days
      Added value: +{
      +  "description": "Trial length in days extracted from deal description text, when present.",
      +  "type": [
      +    "integer",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / deals / items / properties / deal / properties / is_lifetime_plan
      Added value: +{
      +  "description": "True when the description mentions lifetime access or one-time purchase.",
      +  "type": "boolean"
      +}
    • changedOutput schema / properties / deals / items / properties / deal / required
      Previous value: -[
      -  "has_deal",
      -  "code",
      -  "deal_type",
      -  "discount_percent",
      -  "discount_amount",
      -  "credits_amount",
      -  "free_trial_days",
      -  "applies_to",
      -  "terms",
      -  "expires_at",
      -  "raw_text"
      -]New value: +[
      +  "has_deal",
      +  "code",
      +  "deal_type",
      +  "discount_percent",
      +  "discount_amount",
      +  "credits_amount",
      +  "free_trial_days",
      +  "applies_to",
      +  "terms",
      +  "expires_at",
      +  "description_trial_days",
      +  "is_lifetime_plan",
      +  "raw_text"
      +]
  2. Added

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is covered. The description adds genuine provenance context — results are drawn from the same approved offers as the public deals page — which tells the agent the data set is curated rather than arbitrary. It stops short of disclosing pagination, default ordering, or result-size behavior.

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?

Two sentences, front-loaded with the core action and resource, followed by return-content context. No filler or repetition; every clause carries information about what the tool does or what it returns.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so the description is not obligated to enumerate return fields, making the field list somewhat redundant. Against that, an 8-parameter filter tool with 50% schema coverage and no description-level guidance on filters, defaults, or result capping leaves the agent under-equipped to construct correct queries.

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

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 50% across 8 parameters, and the description contributes no parameter-level meaning at all — it never mentions query, sort, task, feature, pricing_model, or the discount thresholds. Fields like sort, pricing_model, and the two min_discount parameters are documented only by their names and enums, leaving a real gap for a filtering-heavy tool.

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 description states a specific verb ('List or search') and resource ('TAAFT partner deals'), making the operation unambiguous. It hints at the sibling relationship with get_deal via 'List or search' versus a single-deal lookup, but never names it explicitly, so differentiation is inferred 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?

The dual framing 'List or search' implies two usage modes (browse everything vs. keyword search), and the note that results mirror the public deals page gives some context. However, there is no explicit guidance on when to use this over get_deal, nor on how filters should be combined or when to omit parameters.

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.