Skip to main content
Glama
PCWProps

Pressable MCP Server

by PCWProps

pressable_delete_site

Remove a WordPress site from the Pressable hosting platform by specifying its ID or name to manage site lifecycles.

Instructions

Delete a specific site.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe site ID or name to delete

Implementation Reference

  • The handler implementation for 'pressable_delete_site' which calls the API delete endpoint.
    handler: async (args) => {
        return await api.delete(`/sites/${args.id}`);
    }
  • The schema definition for 'pressable_delete_site'.
    inputSchema: {
        type: 'object',
        properties: {
            id: { type: 'string', description: 'The site ID or name to delete' }
        },
        required: ['id']
    },
  • tools/sites.js:51-64 (registration)
    The registration block for 'pressable_delete_site' in the tools list.
    {
        name: 'pressable_delete_site',
        description: 'Delete a specific site.',
        inputSchema: {
            type: 'object',
            properties: {
                id: { type: 'string', description: 'The site ID or name to delete' }
            },
            required: ['id']
        },
        handler: async (args) => {
            return await api.delete(`/sites/${args.id}`);
        }
    },
Behavior2/5

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

No annotations are provided, yet the description fails to disclose critical behavioral traits: whether deletion is permanent, if it affects backups, whether it requires confirmation, or what error conditions apply. The term 'Delete' implies destruction but lacks necessary safety context for a mutation tool.

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

Conciseness4/5

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

The single sentence is efficient with no wasted words, and the key action is front-loaded. While appropriately concise in form, it is insufficiently informative in substance given the high-stakes nature of site deletion.

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?

For a destructive operation with zero annotations and no output schema, the description is dangerously incomplete. It omits permanence warnings, recovery options, and side effects that are essential for an agent to invoke this tool safely.

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 coverage is 100% (the 'id' parameter is fully described), establishing a baseline of 3. The main description ('Delete a specific site') implicitly references the id parameter but adds no additional semantic information, syntax details, or usage examples beyond the schema itself.

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?

States a clear verb ('Delete') and resource ('site'), immediately identifying the tool's function. However, it lacks specificity regarding what 'delete' entails (permanent vs soft delete) and does not distinguish from the sibling tool 'pressable_disable_site'.

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?

Provides no guidance on when to use this tool versus alternatives like 'pressable_disable_site' or 'pressable_restore_site'. Contains no warnings about irreversibility or prerequisites for deletion.

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/PCWProps/pressable-mcp-server'

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