Test Monitor
Dry-run a monitor against current data WITHOUT triggering alerts or sending notifications.
What it does:
- Evaluates the monitor’s conditions against current campaign data
- Shows which campaigns would match and which would be skipped
- Does NOT create triggers, send emails, or queue auto-actions
- Useful for verifying a monitor is configured correctly before enabling
When to use:
- “Test my CPA monitor”
- “Would this alert trigger right now?”
- “Check if my monitor is set up correctly”
- “Dry run the budget overspend alert”
Requires the monitor’s alert_id (get from list_monitors).
Authorizations
API key from https://adspirer.ai/keys. Prefix sk_live_. Treat as a secret — never commit.
Headers
Client-generated UUID to make writes idempotent. Strongly recommended for write tools. A repeat call with the same key returns the cached result instead of re-executing. Example: 550e8400-e29b-41d4-a716-446655440000
Body
All tool arguments are wrapped in an arguments object. The fields accepted inside arguments are listed below — required fields are marked with a red asterisk.
Input for dry-running a monitor against current data.
Response
Tool executed successfully. data.text carries the human-readable result (markdown-friendly). data.quota shows your current usage against the plan limit. data.structured appears when the tool emits machine-parseable structured content. data.content appears for tools that return non-text blocks (images, resources).
Returned on HTTP 200. data.text is the primary human-readable output. data.quota is always present for billable calls. data.structured is set only when the tool emits machine-parseable structured content. data.content is set only when the tool emits non-text content blocks.

