Skip to main content
Glama
PCWProps

Pressable MCP Server

by PCWProps
OverviewSchemaRelated ServersScoreDiscussions
JavaScript

pressable_list_dns_zones

Retrieve all DNS zones for WordPress site management through the Pressable API, enabling users to view and manage DNS configurations.

Instructions

Get a list of all DNS zones.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • tools/dns.js:8-10 (handler)
    Handler function for the pressable_list_dns_zones tool which performs a GET request to /dns/zones.
    handler: async () => {
    return await api.get('/dns/zones');
}
  • tools/dns.js:4-11 (registration)
    Registration block for the pressable_list_dns_zones tool definition.
    {
    name: 'pressable_list_dns_zones',
    description: 'Get a list of all DNS zones.',
    inputSchema: { type: 'object', properties: {} },
    handler: async () => {
        return await api.get('/dns/zones');
    }
},

Tool Definition Quality

B3.2/5.0
Behavior2/5

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

No annotations provided, so description carries full burden. While 'Get' implies read-only, it lacks disclosure on pagination behavior, rate limits, maximum results, or the scope of 'all' (account-wide vs site-specific). No mention of what properties the zones contain.

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?

Single sentence, seven words. Every word earns its place: verb (Get), type (list), scope (all), resource (DNS zones). No boilerplate or redundant text.

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

Completeness3/5

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

Adequate for a zero-parameter list operation, but lacks context on pagination or result limits that would be critical for accounts with many zones. Does not clarify if output includes zone IDs needed for sibling tools like `pressable_create_dns_record`.

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?

Zero parameters present (baseline 4). The word 'all' in the description explains why the schema requires no inputs—implicitly confirming the empty schema is intentional for unfiltered retrieval.

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 specific verb (Get/List) and resource (DNS zones) clearly. Uses 'all' to indicate unfiltered scope. However, it could better distinguish from sibling `pressable_get_dns_records` by explicitly contrasting zones (domains) versus records within zones.

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_get_dns_records`. Does not mention prerequisites, permissions, or whether this retrieves account-level or site-specific zones.

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