Skip to main content
Glama

watchlist_webhook

Get pushes instead of polling: set an https URL on your key and Poseidon POSTs the new changes of your watched brands (new ads, stopped ads, more versions, reused media, reach growth) about every hour, signed with HMAC-SHA256 (header Poseidon-Signature: t=…,v1=…; the secret is returned once when the URL is set), retried with backoff for about 15 hours. Each push costs what watchlist_changes costs (5 credits per brand with something new). Without arguments: shows the webhook and its recent deliveries. Free to set.

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

Input Schema

NameRequiredDescriptionDefault
urlNohttps URL that receives the pushes (public address)
testNotrue sends a test push within a minute
removeNotrue removes the webhook

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

With no annotations supplied, the description carries the entire burden and does so: HMAC-SHA256 signing with the exact header format, the secret being returned only once, retries with backoff for ~15 hours, per-push credit cost, free setup, and no-arg inspect behavior. These are non-obvious operational traits an agent could not infer from the schema.

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?

It is a dense single passage but front-loads the core value proposition ('Get pushes instead of polling') and orders the remaining detail sensibly: signing, retries, cost, then no-arg mode. Every clause carries information, though the run-on structure makes it slightly harder to scan.

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 3-parameter, zero-required tool with no output schema, the description covers setup, authentication, delivery cadence, failure retry, cost, removal, test behavior, and the default read mode. An agent has everything needed to call it correctly and to anticipate the response.

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%, so the schema already documents url, test, and remove adequately. The description adds useful context (https requirement implied by 'public address', the secret returned at set time, hourly push cadence) but does not enrich individual parameters beyond what the schema says.

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?

The description states a specific verb and resource ('set an https URL on your key and Poseidon POSTs the new changes') and explicitly frames the tool as an alternative to polling, naming the paid operation it mirrors (watchlist_changes, 5 credits per brand). It also distinguishes the no-argument read mode ('shows the webhook and its recent deliveries'), so an agent can tell the write path from the inspect path.

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?

It gives clear context for when to use it ('Get pushes instead of polling') plus a cost-based comparison to watchlist_changes. It stops short of explicitly saying when not to use it versus sibling tools such as watchlist_changes, so it falls just short of full when/when-not guidance.

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