Skip to main content
Glama
Sign In

Aura Historia

by com.aura-historia
OverviewDiscussionsAdmin

Remove from watchlist

deleteWatchlistProduct
DestructiveIdempotent

Remove a listing from the signed-in user's watchlist by productListingId. Returns an empty object; a listing that is not on the watchlist returns NOT_FOUND, also after an earlier call removed 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": {
      "productListingId": "<productListingId>"
    },
    "name": "deleteWatchlistProduct"
  }
}

Input Schema

NameRequiredDescriptionDefault
productListingIdYesID of the listing (`pl_…`).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / productListingId / description
      Added value: +"ID of the listing (`pl_…`)."
  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 destructive and idempotent annotations, it discloses the empty-object result and precise NOT_FOUND behavior for listings that are absent or were already removed. The repeated-call detail usefully clarifies how idempotency manifests at the API level, while 'signed-in user's' scopes whose data is mutated.

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 compact sentences front-load the operation, resource, user scope, and identifier, then cover the result and failure behavior. Every clause contributes actionable information, with no filler or unnecessary repetition.

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

Completeness5/5

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

For a one-parameter deletion with an output schema and full safety annotations, this supplies the caller-critical scope, success result, absent-item error, and repeat-call semantics. No further parameter or response documentation is needed to invoke it correctly; only optional sibling-routing guidance is absent.

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 coverage is 100%, and the schema already supplies the ID's meaning, required status, string type, and pl_ pattern. The description's 'by productListingId' wording and watchlist-membership error add invocation context but no substantive parameter syntax or validation detail beyond the schema.

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 gives a specific action and resource: removing a listing, rather than deleting the listing itself, from the signed-in user's watchlist by productListingId. This clearly separates it from the watchlist read and add siblings, although it does not explicitly contrast removal with patchWatchlistProduct.

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?

The intended use is clear when the caller has a productListingId and wants to remove that listing for the current user. It also explains absent-item and repeated-call behavior, but provides no explicit when-not guidance or alternative for other kinds of watchlist changes.

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

All Aura Historia toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources