Skip to main content
Glama
PCWProps

Pressable MCP Server

by PCWProps
OverviewSchemaSourceRelated ServersDiscussionsAdmin
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}`);
    }
},

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.4/5.0
Behavior2/5

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

The description only implies a destructive operation, but with no annotations, it fails to disclose reversibility, permissions, side effects, or error behavior. It does not contradict annotations, but it does not compensate for their absence.

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

Conciseness2/5

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

The single sentence is short but merely restates the tool name. It is under-specified and does not earn its place by conveying useful information.

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?

With no output schema and no extra context, a delete tool of this complexity needs at least basic details on return values or failure modes. The description provides none, leaving the agent without enough information for confident invocation.

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

Parameters1/5

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

Schema description coverage is 0%, and the description does not mention either parameter (zone_name, record_id), their formats, or how they interact. No value is added beyond the schema's bare field names.

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 states the verb 'Delete' and the resource 'DNS record', clearly indicating the tool's function. It is unambiguous although it does not explicitly contrast with sibling tools like create_dns_record.

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 is provided on when to use this tool, prerequisites, or how it differs from alternatives. The description lacks any contextual usage information.

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