Skip to main content
Glama

watchlist_edit

Save competitors to watch, on your key: add or remove brands by page_id (get it with find_brand), up to 25. Use it when the user says 'watch these brands', 'add X to my competitors', 'stop watching Y'. Only confirmed e-commerce brands can be added. Returns the watchlist. Free.

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

Input Schema

NameRequiredDescriptionDefault
addNopage ids to add
removeNopage ids to remove

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

No annotations exist, so the description carries the full behavioral burden, and it does disclose key traits: a 25-entry cap, the requirement that only confirmed e-commerce brands can be added, that it returns the watchlist, and that it is free on the user's key. It omits what happens on invalid or over-limit ids and whether removes fail silently for non-watched brands, which is why it falls short of a 5.

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?

A single dense paragraph that front-loads the action, then the cap, then the id prerequisite, then usage triggers, then constraints and return value. Every sentence carries distinct information with no restatement of the name.

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 two-parameter, non-destructive-looking mutation with no output schema, the description covers limits, prerequisites, valid input domain, and return value, which is close to complete. Error and partial-failure semantics remain unspecified, which is the only meaningful 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 coverage is 100%, so the baseline is 3; the description adds real meaning on top by explaining that the ids are page_ids obtained via find_brand and that they are the mechanism for choosing which brands to watch or unwatch. It does not describe array behavior (partial failures, duplicate ids), so it stops short of 5.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: add or remove brands on the user's watchlist by page_id, with a hard cap of 25. It also distinguishes itself from the siblings by pointing to find_brand for page_id lookup and by framing the operation as mutation of the user's own watchlist rather than retrieval.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit trigger phrases ('watch these brands', 'add X to my competitors', 'stop watching Y') plus the prerequisite step of resolving ids via find_brand, so the agent knows both when to call it and what to call first. Nothing about selection is left to inference.

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