Skip to main content
preview_resource_deletion Preview permanent removal of an unused watch, target or project. Returns exact confirmation and blockers. Resources with execution history require historical erasure; pause watches and targets or retire competitor sets to stop future scheduling while preserving evidence.
Available in the deployed MCP and HTTP bundle. Confirm access and inputs with your connected catalog. Workspace scopes and enabled providers still apply.
This read does not start a verification job.

Example request

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

Returned result

Illustrative data validated against the documented response schema. IDs and dates are examples, not a live account capture. 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

Only unused resources without execution or retained shared history qualify. Inspect eligible, blockers and the exact returned confirmation before requesting deletion.

Output fields

Fields inside optional or nullable parents apply only when that parent exists. Common schema conventions explain evidence states, empty lists and extensions.
  • resource_type (string, required): values: “watch”, “target”, “project”
  • resource_id (string, required): Identifier returned by the related operation.
  • project_id (string, required): Project that owns this record.
  • counts (object, required).
  • blockers (array, required).
  • eligible (boolean, required).
  • confirmation (string, required).
  • state (string, required): Saved lifecycle or evidence state, as enumerated for this record.
  • receipt (object / null, required).
  • scope (string, required).
Download input schema · Download output schema

Errors and retries

The command is annotated idempotent. Reuse an accepted idempotency key when the input provides one; changing the payload under a reused key can conflict. 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

delete_resource Follow the related workflow, inspect capability status, or return to the command index.