DESTRUCTIVE

delete_baseline

Deletes a draft baseline with its record rows and versions; a baseline past its draft is the record and is superseded rather than deleted.

Remove a baseline that was never frozen. The draft, its record rows and every version of it are deleted and its name is free again; the records it listed are untouched, since a draft never locked them. A baseline that is in review, approved, awaiting the client's signature, signed or superseded cannot be deleted: it is the record the project was held to, and the answer says to supersede it instead. Marked destructive, so a client confirms before running it. Runs the same action as Delete Baseline in the application and emits baseline.deleted.

Requires ability

The token behind the MCP session must hold it, or the call is refused with TOKEN_MISSING_ABILITY.

Runs the same action as

The REST endpoint and this tool share one action, so validation, permissions and events are identical.

Fires one event

Delivered to every endpoint subscribed to it once the change is made.

Annotations

Destructive

A client that honours annotations asks a person before running it.

Arguments

baseline_id*string

UUID of the draft baseline to delete.

What it returns

{  "data": {    "baseline_id": "6a7b8c9d-0e1f-4a2b-8c3d-4e5f6a7b8c9d",    "deleted": true  }}

How it fails

VALIDATION_FAILED

the baseline is past its draft; nothing is deleted.

RESOURCE_NOT_FOUND

unknown baseline_id, or a baseline outside the token's scope.

FORBIDDEN

the token is a client guest's, or the holder's role on the project does not carry baseline:delete.

TOKEN_MISSING_ABILITY

token lacks baseline:delete.

How is this guide?

Last updated on