Skip to main content
Glama

Subscribe a webhook to Network changes

subscribe_network_webhook

Subscribes an HTTPS URL to signed JSON webhooks for new public changes on a tracker, person, or site, with HMAC signature details for verification and retry handling.

Instructions

Get every new public change on a tracker, a person's trackers or a whole site (e.g. nike.com) POSTed to an https URL as signed JSON ({type: "network.change", id, change: {id, url, title, previousValue, currentValue, summary, origin, publishedAt, watch, hunter}}). Verify X-Monity-Signature = "sha256=" + hex HMAC-SHA256(secret, X-Monity-Timestamp + "." + raw body); the secret is returned here as signing.secret. Retries on 5xx/429/timeouts; a 410 unsubscribes. Needs a write-scope API key. Max 25 per account.

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": {
      "url": "<url>",
      "targetType": "<targetType>",
      "targetRef": "<targetRef>"
    },
    "name": "subscribe_network_webhook"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYeshttps address on the public internet
targetRefYesA tracker's slug or id, a person's handle, or a site such as nike.com
targetTypeYesWhat to follow: WATCH (a tracker with one source) or WATCHLIST (a tracker with several), HUNTER (a person) or SITE

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

A4.1/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 full behavioral burden and does so well: it gives the exact payload shape, the X-Monity-Signature verification formula with timestamp concatenation, retry semantics on 5xx/429/timeouts, the 410-unsubscribes contract, the auth scope required, and the per-account cap.

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 single dense paragraph, but it is front-loaded with the purpose and every clause (payload contract, signature check, retry policy, quota) carries operational weight. Formatting into short lines for the signature rule and limits would improve scanability slightly.

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 3-parameter subscription tool with no annotations and no output schema, this is close to complete: it explains what will be delivered, how to authenticate the delivery, how failures behave, and that signing.secret is returned by the call. The only gap is what the immediate call response contains beyond the secret, and how to later remove a subscription.

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 url, targetRef, and targetType with its four-value enum are already documented. The description restates the accepted target kinds ('a tracker, a person's trackers or a whole site') without adding material meaning beyond the schema, so the baseline of 3 applies.

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 opening clause names the specific verb and resource: it delivers every new public change on a tracker, a person's trackers, or a site, POSTed to an https URL as signed JSON. That is concrete enough to separate it from siblings like get_network_changes (pull) or unsubscribe_network_webhook (teardown).

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?

Usage is implied by the action itself, and the description supplies real preconditions (write-scope API key, max 25 per account), but it never routes the agent to siblings — it does not mention test_network_webhook for validation or unsubscribe_network_webhook for removal, both of which are obvious alternatives in this catalog.

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