Delete Organization Folder

Destructive Deletes a folder. The agents inside it are NOT deleted — they become unfiled. Requires confirm: true. Say plainly that the agents survive, so the user is not scared off a harmless cleanup, and do not describe this as deleting agents.

Parameters

Name	Type	Required	Description
`folder_id`	`string`	Yes	The folder ID — from list_organization_folders
`confirm`	`boolean`	Yes	Must be true. Set this only after the user has explicitly approved deleting this folder.

Complete input schema

{
  "type": "object",
  "properties": {
    "folder_id": {
      "type": "string",
      "description": "The folder ID — from list_organization_folders"
    },
    "confirm": {
      "type": "boolean",
      "description": "Must be true. Set this only after the user has explicitly approved deleting this folder."
    }
  },
  "required": [
    "folder_id",
    "confirm"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

Registered output schema

{
  "type": "object",
  "properties": {
    "deleted": {
      "type": "boolean",
      "description": "True when the folder was deleted"
    },
    "folder_id": {
      "type": "string",
      "description": "The id of the deleted folder"
    }
  },
  "required": [
    "deleted",
    "folder_id"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

Before you call

Connect and initialize the MCP client with OAuth or an API key for the intended workspace.
Provide the required parameters: folder_id, confirm.
Set confirm: true only after the user approves the exact target and action.

Example MCP request

Send tools/call after your client completes MCP initialization. Replace placeholder values with IDs and inputs from your workspace. For object and array parameters, follow the nested requirements in the parameter description instead of treating an empty value as complete.

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "delete_organization_folder",
    "arguments": {
      "folder_id": "folder_abc123",
      "confirm": true
    }
  }
}

Successful results include structuredContent and a text content block containing the same JSON. Check isError first, then read structuredContent or parse content[0].text. See MCP responses and errors for the full envelope and failure behavior.

Verify the result

Confirm the response is not marked isError. Call List Organization Folders to read the affected resource. Verify that the target is removed or disconnected before reporting completion.

Retry safety

This tool can remove or disconnect a resource. Confirm the exact target first, and do not retry after an uncertain result until you verify the current state.

List Organization Folders: list_organization_folders
List My Organizations: list_my_organizations
Get My Organization: get_my_organization

Start Here

Tool Reference

Parameters

Complete input schema

Registered output schema

Before you call

Example MCP request

Verify the result

Retry safety

​Parameters

​Complete input schema

​Registered output schema

​Before you call

​Example MCP request

​Verify the result

​Retry safety

​Related MCP tools

​Related guides

Parameters

Complete input schema

Registered output schema

Before you call

Example MCP request

Verify the result

Retry safety

Related MCP tools

Related guides