Skip to main content
Glama
oborseth

Official Porkbun MCP Server

by oborseth
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Delete Hosting File

delete_hosting_file
DestructiveIdempotent

Remove a file or directory from Porkbun Secure Static Hosting. Supports recursive deletion of non-empty directories up to 2,000 items.

Instructions

Delete a file or directory at path in a domain's Secure Static Hosting space. Idempotent: a path that is already gone succeeds with alreadyAbsent: true, so there is no need to re-check before retrying. A directory that still has files fails with HOSTING_DIR_NOT_EMPTY and lists its contents; pass recursive: true to delete a directory with everything in it in one call (up to 2,000 items; the site root can never be deleted). To clear out a site, delete its top-level entries with recursive: true rather than file by file. Calls the Porkbun Hosting API (https://porkbun.com/llms/hosting).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesPath to delete, e.g. `old/page.html` or `assets`.
domainYesDomain whose hosting file to delete.
recursiveNoDelete a directory together with everything inside it. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.41.1
    • changedInput schema / properties / path / description
      Previous value: -"Path to delete, e.g. `old/page.html`."New value: +"Path to delete, e.g. `old/page.html` or `assets`."
    • addedInput schema / properties / recursive
      Added value: +{
+  "description": "Delete a directory together with everything inside it. Default false.",
+  "type": "boolean"
+}
  2. Addedv0.39.4

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the annotations (destructive/idempotent hints) by disclosing concrete semantics: already-absent paths return alreadyAbsent: true, non-empty directories fail with HOSTING_DIR_NOT_EMPTY and list contents, recursive caps at 2,000 items, and the site root is undeletable. This is exactly the failure/limit context an agent needs.

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?

Front-loads the core action, then each subsequent sentence carries distinct load: idempotency, error behavior, recursive semantics, and the recommended bulk strategy. No filler or restatement of the name.

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

Completeness5/5

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

With no output schema, the description still communicates what the call returns on the interesting cases (alreadyAbsent flag, error code plus contents list) and the practical limits. Nothing needed to invoke it correctly is missing.

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 description coverage is 100% (baseline 3), and the description adds real meaning on top: it explains what recursive actually does (delete a directory with everything inside, up to 2,000 items) and constrains path (root cannot be deleted). It adds little on domain, hence not a 5.

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 (delete) and resource (file or directory) and scopes it precisely to 'a domain's Secure Static Hosting space', which separates it from service-level tools like delete_hosting and from make_hosting_dir/list_hosting_files. An agent can select it without opening the schema.

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 clear operational guidance: no need to pre-check because of idempotency, use recursive instead of file-by-file to clear a site, and recursive handles directories with contents. It does not explicitly name sibling tools (e.g., delete_hosting vs. this) or state prerequisites such as domain ownership, so it stops just short of a 5.

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

Deploy Server

Other Tools