Skip to main content
Glama
PCWProps

Pressable MCP Server

by PCWProps
OverviewSchemaRelated ServersScoreDiscussions
JavaScript

pressable_delete_dns_record

Remove a DNS record from a Pressable WordPress site's domain zone by specifying the zone name and record ID.

Instructions

Delete a specific DNS record.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
zone_nameYes
record_idYes

Implementation Reference

  • tools/dns.js:47-60 (handler)
    The tool definition and handler for 'pressable_delete_dns_record'.
        name: 'pressable_delete_dns_record',
    description: 'Delete a specific DNS record.',
    inputSchema: {
        type: 'object',
        properties: {
            zone_name: { type: 'string' },
            record_id: { type: 'string' }
        },
        required: ['zone_name', 'record_id']
    },
    handler: async (args) => {
        return await api.delete(`/dns/zones/${args.zone_name}/records/${args.record_id}`);
    }
},

Tool Definition Quality

C2.6/5.0
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 but fails to mention critical traits: whether deletion is permanent/irreversible, what happens if the record_id doesn't exist, or what the operation returns (success/failure).

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

Conciseness3/5

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

A single sentence of four words is appropriately concise, but 'specific' is slightly redundant and the description lacks front-loaded critical warnings appropriate for a destructive operation.

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 schema annotations and no output schema, the description is inadequate. It omits safety warnings, error conditions, and parameter relationships that would be necessary for safe agent operation.

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

Parameters2/5

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

Schema description coverage is 0% yet the description adds no semantic context for zone_name or record_id. While 'specific DNS record' loosely implies identification is needed, the description fails to clarify zone boundaries or ID formats, leaving parameters effectively undocumented.

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 clearly states the verb (Delete) and resource (DNS record), distinguishing it from sibling tools pressable_create_dns_record and pressable_get_dns_records. However, it stops short of describing the scope mechanism (by zone and ID) which would make it a 5.

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?

No guidance provided on when to use this tool versus alternatives, nor any mention of prerequisites (e.g., needing to fetch record IDs via pressable_get_dns_records first) or warnings about permanent 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