Kiro MCP Server

Delete a Kiro session

kiro_session_delete

Destructive

Permanently delete a Kiro session from the store. It closes the session first when attached and requires confirm: true, so use it to remove finished or unwanted coding sessions.

Instructions

Permanently delete a session from Kiro's store (session/delete), like kiro-cli chat --delete-session. Requires confirm: true. Closes the session first when it is attached. Local sessions must live inside KIRO_MCP_ROOTS.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "session_id": "<session_id>"
    },
    "name": "kiro_session_delete"
  }
}

Input Schema

Name	Required	Description	Default
`confirm`	No
`session_id`	Yes	Kiro session id (sess_<uuid>).

Output Schema

Name	Required	Description	Default
`deleted`	Yes
`session_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Nov 5, 2026

TDQS

A4.2/5.0

Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false and idempotentHint=false, so the safety profile is largely covered. The description does add value beyond them by disclosing that confirm: true is required and that attached sessions are closed first, but it does not describe failure modes (invalid id, path outside KIRO_MCP_ROOTS) or what happens to session artifacts on disk.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences, each carrying distinct information: destructive action, backing method, prerequisite flag, side effect, and path constraint. Nothing is repeated and the irreversible nature is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be explained, and the description covers irreversibility, the confirm gate, and the root-path restriction. It is complete enough to invoke safely, with only error behaviour left unspecified.

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 only 50% (confirm has no schema description), so the description must compensate, and it does by stating 'Requires confirm: true' — giving both the value and the obligation. The session_id parameter is handled by the schema's pattern and description, so little is lost.

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 and resource ('Permanently delete a session'), names the backing method (session/delete), and anchors it to a CLI equivalent. The word 'permanently' plus 'Closes the session first when it is attached' cleanly separates it from siblings like kiro_session_close and kiro_session_compact.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives real usage context: a confirm flag is mandatory, attached sessions are closed first, and local sessions must reside under KIRO_MCP_ROOTS. It stops short of explicitly routing to an alternative (e.g. 'use kiro_session_close to detach without deleting'), so the when-not guidance is only implied by the word 'permanently'.

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