Skip to main content
Glama

Add to watchlist

addWatchlistProduct
Idempotent

Add a listing to the signed-in user's watchlist by productListingId so they can follow it and, with notifications on (the default), hear about changes. A listing already on the watchlist returns CONFLICT; subscription tier limits apply.

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": {
      "productListingId": "<productListingId>"
    },
    "name": "addWatchlistProduct"
  }
}

Input Schema

NameRequiredDescriptionDefault
notificationsNoWhether to be notified about changes to the listing (default true).
productListingIdYesID of the listing (`pl_…`) to add.

Output Schema

NameRequiredDescriptionDefault
stateYes
userIdYes
createdNo
updatedNo
notificationsYes
productListingIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / notifications / description
      Added value: +"Whether to be notified about changes to the listing (default true)."
    • addedInput schema / properties / productListingId / description
      Added value: +"ID of the listing (`pl_…`) to add."
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=true, so the description only needs to add context. It usefully adds the default notification behavior and the CONFLICT-on-duplicate response, but the CONFLICT behavior sits in tension with idempotentHint=true without explanation, and the vague 'subscription tier limits apply' is not actionable (no limit value, no error code).

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?

Two tight sentences with the action and keying parameter front-loaded, and the failure condition placed second where it belongs. Minor redundancy in 'so they can follow it and ... hear about changes', which partly repeats the notifications clause.

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?

An output schema exists, so return values need no explanation, and the annotations carry the safety profile. The only substantive gap is the unquantified tier-limit warning, which leaves the agent unable to predict the failure mode.

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%, including the pattern and the notifications default, so the baseline is 3. The description restates the notifications default rather than adding new meaning, and adds nothing about the ID format beyond what the schema already encodes.

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 (add), resource (watchlist entry) and keying parameter (productListingId), plus the user-facing outcome ('so they can follow it'). The action is unambiguous against siblings like deleteWatchlistProduct and patchWatchlistProduct, though it never names them explicitly.

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?

It establishes the condition for failure ('a listing already on the watchlist returns CONFLICT') and warns that 'subscription tier limits apply', which is a partial when-not signal. It does not say when to prefer this over alternatives or what prerequisites (auth state, tier check) must hold before calling.

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