Skip to main content
Glama

Stop watching a product

stop_watching
DestructiveIdempotent

Removes a product from the signed-in account's Deal.ai wish list, and stops its price-drop e-mails, including those from a search that found it.

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": {
      "product": "<product>"
    },
    "name": "stop_watching"
  }
}

Input Schema

NameRequiredDescriptionDefault
productYesA product_id from search_products or ask_deal_ai, or the link to a product's page on deal.ai (https://deal.ai/p/...).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already disclose destructiveHint=true and idempotentHint=true, so the destructive profile is covered. The description still earns credit for disclosing a non-obvious second effect — that email suppression also covers alerts originating from a search that surfaced the product — but it omits the outcome when nothing is watched and whether the action is reversible.

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?

The action is front-loaded in a single tight sentence with no filler. The trailing clause on search-sourced emails is slightly dense but genuinely informative rather than redundant.

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 one-parameter destructive mutation with rich annotations and full schema coverage, the description covers both material effects (wish list removal and email cancellation). It is nearly complete, lacking only failure/no-op behavior and re-watch guidance.

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

Parameters3/5

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

Schema description coverage is 100% and the single 'product' parameter already documents accepted forms (product_id or deal.ai URL). The description adds no syntax or format detail beyond the schema, so the baseline applies.

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 names a specific verb and resource ('Removes a product from the signed-in account's Deal.ai wish list') and adds the email-unsubscribe side effect, which clearly marks it as the inverse of watch_price. It never names that sibling explicitly, so the 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?

Usage is implied by the verb 'Removes' and the act of stopping emails, but there is no explicit when-to-use guidance, no mention of the sibling to use instead for adding a watch (watch_price), and no note on what happens if the product is not currently watched.

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.