Skip to main content
Glama
PCWProps

Pressable MCP Server

by PCWProps
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript

pressable_create_site

Create a new WordPress site with configurable PHP version, datacenter location, and installation options through the Pressable API.

Instructions

Create a new WordPress site.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesThe name of the site
datacenterNoDatacenter ID
php_versionNoPHP version (e.g., 8.1)
install_optionNoInstall option (e.g., "none", "wp_latest")

Implementation Reference

  • tools/sites.js:34-50 (handler)
    The definition of the 'pressable_create_site' tool, including its schema and the handler that calls the Pressable API to create a site.
    {
    name: 'pressable_create_site',
    description: 'Create a new WordPress site.',
    inputSchema: {
        type: 'object',
        properties: {
            name: { type: 'string', description: 'The name of the site' },
            datacenter: { type: 'string', description: 'Datacenter ID' },
            php_version: { type: 'string', description: 'PHP version (e.g., 8.1)' },
            install_option: { type: 'string', description: 'Install option (e.g., "none", "wp_latest")' }
        },
        required: ['name']
    },
    handler: async (args) => {
        return await api.post('/sites', args);
    }
},

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

Given no annotations are provided, the description carries the full burden for behavioral disclosure. It only states that a site is created, but does not mention side effects such as potential costs, required permissions, irreversibility, or whether the operation is synchronous. This is a minimal disclosure, similar to a mutation tool without annotations.

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 concise sentence with zero wasted words. It is front-loaded with the action and object, making it easy to parse and process. The length is entirely appropriate for the simplicity of the task.

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?

Without an output schema and with no annotations, the description is incomplete for a create operation. It lacks context about what the response looks like, whether the operation is immediate, any prerequisites, and the real-world effects (e.g., billing, provisioning time). A new WordPress site creation likely has nuances that are not covered.

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 input schema has 100% coverage for its four parameters, each with a clear description. The tool description itself adds no parameter-specific information, so the schema does the heavy lifting. Per the rubric, baseline 3 is appropriate when schema coverage is high and description adds no additional meaning.

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 the specific verb 'Create' plus the resource 'a new WordPress site', clearly indicating the action. This distinguishes it from sibling tools like pressable_list_sites or pressable_delete_site, and even adds 'WordPress' beyond the tool name, making the purpose 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, no preconditions, and no exclusions. It simply states the action without any contextual advice or mention of alternatives, leaving the agent without decision-support 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