Skip to main content
Glama
Sign In

apis-io

by io.apis
OverviewDiscussionsAdmin

watch_listing

Idempotent

INFLUENCE — be told when a listing you care about moves: score changes, band changes, agent-band changes, or a check closing. REQUIRES a destination: contact (an email address), callback_url (an https endpoint that receives signed JSON), or both. The first pass after registering records where the provider stands and sends nothing, so the first notification you get is about a real move. agent_band is the one worth having — it carries the gate that caused the change, which a provider cannot compute about themselves. Re-registering the same slug REPLACES its event set rather than adding a second watch. list_watches shows what you hold; unwatch_listing removes one. Priced B1 (single-entity synthesis) — $0.01 per call under pay-as-you-go; included in Understanding and Influence. See apis://prices.

Input Schema

NameRequiredDescriptionDefault
slugYesProvider slug of the listing, as find_providers returns it, e.g. "stripe".
eventsNoscore, band, agent_band, check. Defaults to all four.
contactNoEmail address for notifications.
contextNoOptional: one sentence on why you are asking. Never used to rank; read only if a result is wrong.
callback_urlNoHTTPS endpoint for signed webhook delivery.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / context / description
      Previous value: -"Optional: why you are asking. One sentence — the task you are trying to complete, or what you expect to get back. Never included in the answer and never used to rank; it is read only when a result turns out to be wrong, which is when knowing the intent is what makes the report actionable."New value: +"Optional: one sentence on why you are asking. Never used to rank; read only if a result is wrong."
  2. Changed1 schema field changed
    • addedInput schema / properties / slug / description
      Added value: +"Provider slug of the listing, as find_providers returns it, e.g. \"stripe\"."
  3. Changed3 schema fields changed
    • addedInput schema / properties / callback_url
      Added value: +{
+  "description": "HTTPS endpoint for signed webhook delivery.",
+  "type": "string"
+}
    • addedInput schema / properties / contact
      Added value: +{
+  "description": "Email address for notifications.",
+  "type": "string"
+}
    • changedInput schema / properties / events / description
      Previous value: -"score, band, check. Defaults to all three."New value: +"score, band, agent_band, check. Defaults to all four."
  4. Added

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the annotations: explains the baseline first-pass behavior ('records where the provider stands and sends nothing'), the signed-JSON webhook delivery, why agent_band is the valuable event (it carries the gate a provider cannot self-compute), replace-vs-append semantics, and pricing (B1, $0.01/call). This is exactly the kind of context annotations cannot carry.

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 purpose and requirement, then supporting detail. It is dense and slightly long for a watch tool, but nearly every sentence carries operational information (destinations, baseline behavior, replace semantics, pricing).

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?

With no output schema, the description still covers return behavior (first pass sends nothing), delivery channels, event defaults, idempotent replace semantics, and pricing. An agent has everything needed to call it correctly on the first try.

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 already 100%, so the baseline is 3, but the description adds real meaning: contact must be an email, callback_url must be HTTPS signed JSON, and events default to all four. The note that agent_band carries the causal gate is genuine semantic value not present in 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?

States a specific verb+resource ('be told when a listing you care about moves') and enumerates the exact event types it watches: score, band, agent_band, check. It explicitly distinguishes itself from the sibling tools list_watches and unwatch_listing, so an agent can route without opening schemas.

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 prerequisites ('REQUIRES a destination: contact, callback_url, or both') and names the alternatives with their roles: list_watches shows what you hold, unwatch_listing removes one. The replace-on-re-register behavior further guides correct invocation.

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

All apis-io toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources