Skip to main content
Glama
PCWProps

Pressable MCP Server

by PCWProps
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript

pressable_list_site_domains

Retrieve all domains associated with a specific WordPress site to manage DNS configurations and verify site accessibility.

Instructions

Get a list of domains for a specific site.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes

Implementation Reference

  • tools/sites.js:178-188 (handler)
    The handler and schema definition for the pressable_list_site_domains tool.
        name: 'pressable_list_site_domains',
    description: 'Get a list of domains for a specific site.',
    inputSchema: {
        type: 'object',
        properties: { id: { type: 'string' } },
        required: ['id']
    },
    handler: async (args) => {
        return await api.get(`/sites/${args.id}/domains`);
    }
},

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are present, so the description must carry the full burden of behavioral disclosure. It only states the basic operation without mentioning read-only intent, return format, error behavior, or any side effects. The name 'list' implies safety, but this is not explicit.

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 is a single, succinct sentence that front-loads the key information. It contains no irrelevant words or repeated schema details, earning a high score for structure and conciseness.

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?

Given the tool's simplicity (one parameter, list operation), the description captures the core purpose adequately. However, it lacks information about return structure, permissions, or edge cases, which would be useful for an agent invoking the tool, so it remains minimally viable.

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 schema has one 'id' parameter with 0% description coverage. The description's phrase 'for a specific site' provides minimal context that the id refers to a site identifier, partially compensating for the lack of schema descriptions, though it does not specify format or constraints.

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

Purpose5/5

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

The description uses a specific verb 'Get' and clearly identifies the resource as a list of domains scoped to a specific site, distinguishing it from siblings like pressable_list_sites and pressable_add_site_domain. It is concise and unambiguous.

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, nor does it mention exclusions or prerequisites. It simply states what the tool does without any contextual or alternative-based usage hints.

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