ftp-deploy-mcp

Overview Schema Source Related Servers Discussions Admin

Delete a remote file or directory

ftp_delete

DestructiveIdempotent

Delete a remote file or directory on FTP/FTPS/SFTP servers. Use recursive to remove directories; the server root is never deleted.

Instructions

Delete a remote file, or a directory when recursive:true. Never deletes the server root.

Input Schema

TableJSON Schema

Name	Required	Description
`path`	Yes	Remote path to delete, relative to the server root.
`server`	No	Name of the configured server. Defaults to the configured default, or the sole server.
`recursive`	No	Required to delete a directory and its contents.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.2.0Sep 9, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "oneOf": [
+    {
+      "additionalProperties": false,
+      "properties": {
+        "deleted": {
+          "type": "boolean"
+        },
+        "entry_type": {
+          "enum": [
+            "file",
+            "directory"
+          ],
+          "type": "string"
+        },
+        "path": {
+          "type": "string"
+        },
+        "recursive": {
+          "type": "boolean"
+        },
+        "security_warning": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "server": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "server",
+        "path",
+        "entry_type",
+        "recursive",
+        "deleted",
+        "security_warning"
+      ],
+      "type": "object"
+    },
+    {
+      "additionalProperties": false,
+      "properties": {
+        "error": {
+          "additionalProperties": false,
+          "properties": {
+            "code": {
+              "enum": [
+                "CONFIG_REQUIRED",
+                "CONFIG_INVALID",
+                "SERVER_REQUIRED",
+                "SERVER_UNKNOWN",
+                "INVALID_ARGUMENT",
+                "READ_ONLY",
+                "TRANSPORT_POLICY",
+                "HOST_KEY_REJECTED",
+                "REMOTE_ROOT_REJECTED",
+                "PATH_REJECTED",
+                "NOT_FOUND",
+                "ALREADY_EXISTS",
+                "TRANSFER_LIMIT",
+                "TRANSFER_VERIFY",
+                "TARGET_CHANGED",
+                "CANCELLED",
+                "TIMEOUT",
+                "DEPLOY_PARTIAL",
+                "TRANSPORT_ERROR",
+                "OUTPUT_LIMIT",
+                "INTERNAL_ERROR",
+                "SCAN_LIMIT",
+                "CAPACITY_LIMIT"
+              ],
+              "type": "string"
+            },
+            "effects": {
+              "enum": [
+                "none",
+                "possible",
+                "confirmed"
+              ],
+              "type": "string"
+            },
+            "message": {
+              "type": "string"
+            },
+            "next_action": {
+              "enum": [
+                "fix_input",
+                "fix_config",
+                "select_server",
+                "inspect_target",
+                "retry",
+                "contact_operator",
+                "none"
+              ],
+              "type": "string"
+            },
+            "partial": {
+              "additionalProperties": false,
+              "properties": {
+                "completed_bytes": {
+                  "maximum": 9007199254740991,
+                  "minimum": 0,
+                  "type": "integer"
+                },
+                "completed_files": {
+                  "maximum": 9007199254740991,
+                  "minimum": 0,
+                  "type": "integer"
+                },
+                "failed_files": {
+                  "maximum": 9007199254740991,
+                  "minimum": 0,
+                  "type": "integer"
+                },
+                "final": {
+                  "type": "boolean"
+                },
+                "total_files": {
+                  "maximum": 9007199254740991,
+                  "minimum": 0,
+                  "type": "integer"
+                }
+              },
+              "required": [
+                "completed_files",
+                "completed_bytes",
+                "failed_files",
+                "final"
+              ],
+              "type": "object"
+            },
+            "request_id": {
+              "format": "uuid",
+              "type": "string"
+            },
+            "retryable": {
+              "type": "boolean"
+            },
+            "schema_version": {
+              "const": 1,
+              "type": "number"
+            }
+          },
+          "required": [
+            "schema_version",
+            "code",
+            "message",
+            "retryable",
+            "request_id",
+            "next_action",
+            "effects"
+          ],
+          "type": "object"
+        }
+      },
+      "required": [
+        "error"
+      ],
+      "type": "object"
+    }
+  ],
+  "type": "object"
+}

First observedv0.1.0Jul 22, 2026

TDQS

A4.2/5.0

Behavior4/5

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

The description adds valuable behavioral detail beyond annotations: recursive deletion applies to directories, and the server root is protected. The annotations already signal destructive/idempotent behavior, so the description's extra guardrail and recursive qualification are strong contributions.

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?

Two short sentences with the core action front-loaded and the safety constraint immediately after. No filler or repeated schema boilerplate.

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?

The description gives the core behavior, the recursive condition, and a critical root-safety guard. It does not address errors, permissions, or edge cases like nonexistent paths, but for a simple destructive operation with strong annotations and schema coverage, it is reasonably complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is high (all parameters documented). The description adds no new parameter semantics beyond restating that recursive deletion applies to directories, so the schema carries the explanatory burden.

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?

The description uses a specific verb ('Delete'), identifies the target ('remote file' or 'directory'), and includes the recursive condition for directories. This clearly distinguishes it from sibling operations like ftp_read, ftp_upload, and ftp_list.

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?

The description clearly states when the tool applies (files and directories with recursive=true) and adds a meaningful safety exclusion ('Never deletes the server root'). It does not directly compare with sibling tools, but no sibling covers deletion, so the usage context is sufficient.

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

Deploy Server