Skip to main content
set_prospect_monitoring Explicitly enable or pause recurring checks for a saved exact-page opportunity at its current revision. A recent complete verification is reused before the next scheduled source check; enabling does not declare a verified placement.
Name recorded in the 2026-10-27 deployment. This page describes current source; verify inputs and access in your connected catalog. Provider configuration and workspace access still apply.
This explicit action changes scheduled checking. Enabling requires ordinary credit and capacity admission; later scheduled checks consume their normal allowance. Disabling pauses future scheduling.

Example request

Connect through MCP, CLI, or HTTP. Replace example identifiers with records from your workspace.

Returned result

Schema-validated example; IDs and dates are illustrative. MCP returns this data in structuredContent and in a text content block; generic HTTP and CLI return the JSON result directly.

Input fields

Omit optional fields when you do not want to supply them. Null is accepted only where listed. Unknown input properties are rejected.

Validation and omitted values

Use the current revision and choose enabled true or false explicitly. Omitted cadenceSeconds preserves the saved cadence. This starts or pauses future source checks; it does not send outreach or declare a live placement. Enabling needs an exact source page and an unarchived, non-retired record within the current allowance. Enabling itself spends no check credits; future checks consume allowance when admitted. Review the monitoring estimate before starting. A recent complete one-time verification supplies the first observation; the next check uses the saved cadence and any earlier confirmation or Retry-After constraint. Pausing retains evidence and the saved schedule slot. After an uncertain response, read get_prospect and compare enabled, cadence and revision before deciding whether another mutation is needed. Existing active or paused preferences change only as explicitly requested.

Output fields

Fields inside optional or nullable parents apply only when that parent exists. Common schema conventions explain evidence states, empty lists and extensions.
  • prospect (object, required).
  • replayed (boolean, required): True when the response reuses an earlier request with the same idempotency value.
Types, allowed values, limits and nested fields:
Download input schema · Download output schema

Errors and retries

This write is annotated idempotent without a caller-supplied idempotency key. Reconcile saved state after an uncertain response, then use the same inputs for the same intended operation. Do not add an unsupported key. Operation-specific errors include UNAUTHORIZED, INSUFFICIENT_SCOPE, CAMPAIGNS_NOT_READY, PROSPECT_ACCESS_DENIED, INVALID_PROSPECT_INPUT, PROSPECT_NOT_FOUND, PROSPECT_REVISION_CONFLICT, PROSPECT_SOURCE_REQUIRED, ADMISSION_REJECTED, WATCH_QUOTA_EXCEEDED. See error recovery for status, scope, cooldown, cursor and retry handling. Unknown observations are result data and do not establish loss.

HTTP resource routes

This operation has no separate resource alias. Use its generic command route in a matching environment.

Continue

get_prospect · estimate_usage Follow the related workflow. See capability status for availability or the command index for another operation.