Skip to main content
Glama

deleteSite

Remove a Netlify site by providing its ID or name to manage your deployment environment.

Instructions

Delete a site

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
siteIdYesID or name of the site to delete

Implementation Reference

  • Handler implementation for the deleteSite tool. Validates the siteId argument, performs a DELETE request to the Netlify API endpoint `/sites/${siteId}`, and returns a success message or appropriate error.
    case 'deleteSite': {
      const args = request.params.arguments as unknown as DeleteSiteArgs;
      if (!args?.siteId) {
        throw new McpError(
          ErrorCode.InvalidParams,
          'Missing required parameter: siteId'
        );
      }
      try {
        await this.axiosInstance.delete(`/sites/${args.siteId}`);
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify({
                success: true,
                message: `Site ${args.siteId} deleted successfully`,
              }, null, 2),
            },
          ],
        };
      } catch (error) {
        if (axios.isAxiosError(error)) {
          if (error.response?.status === 404) {
            throw new McpError(
              ErrorCode.InvalidParams,
              `Site not found: ${args.siteId}`
            );
          }
          throw new McpError(
            ErrorCode.InternalError,
            `Failed to delete site: ${this.formatNetlifyError(error)}`
          );
        }
        throw error;
      }
    }
  • TypeScript interface defining the input arguments for the deleteSite tool, requiring a siteId string.
    interface DeleteSiteArgs {
      siteId: string;
    }
  • src/index.ts:181-194 (registration)
    Tool registration in the listTools response, including name, description, and input schema for deleteSite.
    {
      name: 'deleteSite',
      description: 'Delete a site',
      inputSchema: {
        type: 'object',
        properties: {
          siteId: {
            type: 'string',
            description: 'ID or name of the site to delete',
          },
        },
        required: ['siteId'],
      },
    },
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Delete a site' implies a destructive, irreversible mutation, but it doesn't specify permissions required, whether deletion is permanent, what happens to associated resources, or error conditions. This is a significant gap for a destructive operation with zero annotation coverage.

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?

The description 'Delete a site' is extremely concise—a single three-word phrase that front-loads the core action. There is zero wasted language, making it efficient and immediately clear, though this conciseness comes at the cost of completeness in other dimensions.

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

Completeness2/5

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

Given this is a destructive mutation tool with no annotations and no output schema, the description is insufficiently complete. It doesn't explain what 'delete' entails behaviorally, what the response might contain, or error handling. For a tool that permanently removes resources, more context is needed to guide safe and effective use.

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?

The input schema has 100% description coverage, with the 'siteId' parameter fully documented as 'ID or name of the site to delete'. The description adds no additional parameter information beyond what the schema provides, so it meets the baseline of 3 where the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Delete a site' clearly states the verb (delete) and resource (site), making the tool's function immediately understandable. It doesn't explicitly differentiate from sibling tools like 'getSite' or 'listSites', but the action 'delete' inherently distinguishes it from those read-only operations.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing an existing site), consequences of deletion, or when to choose other tools like 'createSiteFromGitHub' for creation instead. This leaves the agent without context for appropriate tool selection.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/MCERQUA/netlify-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server