Skip to main content
Glama
PCWProps

Pressable MCP Server

by PCWProps

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

  • 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);
        }
    },
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It identifies the operation as creation (mutation) but fails to specify idempotency behavior, what happens if the site name exists, whether creation is synchronous, or what the response structure looks like.

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?

Extremely concise at only four words. While not padded with fluff, it is arguably underspecified given the tool complexity (4 parameters, no annotations, mutation operation). The single sentence earns its place but leaves significant explanatory gaps.

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 the lack of output schema and annotations, and the presence of 4 parameters including optional configuration choices (datacenter, PHP version), the description is incomplete. It omits return value structure, error scenarios, and site provisioning side effects that would help an agent handle the response.

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 100% schema description coverage, the baseline is 3. The description mentions no parameters, but the schema adequately documents all four fields including examples for php_version and install_option. No additional semantic context (e.g., datacenter selection implications) is provided in the description.

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 a clear verb (Create) and resource (WordPress site). The word 'new' helps distinguish from sibling mutation tools like pressable_update_site and pressable_restore_site. However, it omits the Pressable platform context which could help distinguish from generic WordPress site creation tools.

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_restore_site (which might restore an existing site instead of creating fresh) or pressable_convert_site. No prerequisites, limits, or error conditions are mentioned.

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