Skip to main content
Glama
PCWProps

Pressable MCP Server

by PCWProps

pressable_add_site_domain

Add a custom domain to a WordPress site managed through Pressable, enabling you to connect your own web address for public access.

Instructions

Add a domain to a site.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
domainYes

Implementation Reference

  • The handler function for the pressable_add_site_domain tool, which performs a POST request to add a domain to a site.
    name: 'pressable_add_site_domain',
    description: 'Add a domain to a site.',
    inputSchema: {
        type: 'object',
        properties: {
            id: { type: 'string' },
            domain: { type: 'string' }
        },
        required: ['id', 'domain']
    },
    handler: async (args) => {
        return await api.post(`/sites/${args.id}/domains`, { domain: args.domain });
    }
Behavior2/5

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

With zero annotations provided, the description carries the full burden of behavioral disclosure, yet reveals nothing about side effects, idempotency, required permissions, or whether the operation triggers DNS validation. It mentions 'Add' implying mutation, but omits critical behavioral context like whether this makes the domain primary or additional.

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?

The single sentence is front-loaded and contains no fluff, but extreme brevity becomes under-specification given the lack of annotations and schema documentation. While structurally efficient, the description is inappropriately sized for the information gaps it leaves unfilled.

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?

Given zero annotations, 0% schema coverage, and no output schema, the description is incomplete. For a two-parameter mutation tool, it should explain parameter semantics, behavioral side effects, or return value expectations, but provides only the bare action statement.

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?

With 0% schema description coverage (both 'id' and 'domain' lack descriptions), the description provides minimal semantic mapping by implying 'id' refers to a site and 'domain' is the domain to attach. However, it fails to compensate for the schema gaps by explaining formats (e.g., whether domain includes protocol), whether id is a UUID or slug, or providing examples.

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

Purpose2/5

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

The description 'Add a domain to a site' is tautological—it merely restates the tool name (pressable_add_site_domain) in sentence form without adding specificity. While it identifies the verb (Add) and resources (domain, site), it fails to distinguish this tool from siblings like pressable_create_dns_record or clarify what 'add' entails (attach, map, verify?).

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 (e.g., pressable_create_dns_record for DNS configuration), prerequisites (domain ownership verification requirements), or exclusions. The description states only what the tool does, not when to invoke it.

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