Skip to main content
Glama

watchlist_changes

What changed across ALL your watched competitors since a date, in one call. Use it for 'what's new from my competitors', 'weekly competitor report'. Same content, dates and sources as brand_changes, grouped by brand; brands with no change are listed apart. Also says how many watched ads have at least two reach readings since the date (reach growth can only be shown for those). Costs 5 credits per brand that changed; 0 if none did.

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_changes"
  }
}

Input Schema

NameRequiredDescriptionDefault
sinceNodefault: 7 days ago

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses cost (5 credits per changed brand, 0 if none), the zero-change listing behaviour ('brands with no change are listed apart'), and a caveat that reach growth is only computable for ads with two readings. It omits auth/permission needs and response shape, which keeps it from 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core scope in sentence one, then progressively narrows to sibling comparison, empty-case handling, and cost. Dense but every sentence carries information; the reach-readings sentence is the only one that could be tightened.

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?

Adequate for a one-parameter tool with no output schema: grouping, empty-brand handling, and pricing are covered. However, the actual return shape (what a 'change' record contains) is only alluded to via the brand_changes comparison, leaving some ambiguity about what the agent will receive.

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 single 'since' parameter already documents its date format and 7-day default. The description reinforces the semantics by noting the date also gates the reach-reading count, but adds no format or boundary detail beyond the schema.

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?

Specific verb and resource ('what changed across ALL your watched competitors since a date, in one call') with explicit scope ('watched', 'ALL'). It names the sibling it parallels and the exact difference: 'Same content, dates and sources as brand_changes, grouped by brand.'

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 concrete invocation phrasings ('what's new from my competitors', 'weekly competitor report') and an explicit alternative-and-difference statement against brand_changes based on grouping. No when-not exclusion is stated, but the routing decision is unambiguous.

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