Skip to main content
Glama
PCWProps

Pressable MCP Server

by PCWProps

pressable_update_site

Update settings for a WordPress site, including its name and PHP version, through the Pressable API.

Instructions

Update settings for a specific site.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
nameNo
php_versionNo

Implementation Reference

  • The handler function for 'pressable_update_site' tool that performs a PUT request to update the site settings.
    handler: async (args) => {
        const { id, ...data } = args;
        return await api.put(`/sites/${id}`, data);
    }
  • The input schema definition for 'pressable_update_site' tool, defining the required ID and optional parameters like name and PHP version.
    inputSchema: {
        type: 'object',
        properties: {
            id: { type: 'string' },
            name: { type: 'string' },
            php_version: { type: 'string' }
        },
        required: ['id']
    },
  • tools/sites.js:161-176 (registration)
    The full definition and registration of the 'pressable_update_site' tool within the siteTools array.
        name: 'pressable_update_site',
        description: 'Update settings for a specific site.',
        inputSchema: {
            type: 'object',
            properties: {
                id: { type: 'string' },
                name: { type: 'string' },
                php_version: { type: 'string' }
            },
            required: ['id']
        },
        handler: async (args) => {
            const { id, ...data } = args;
            return await api.put(`/sites/${id}`, data);
        }
    },
Behavior2/5

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

No annotations are provided, so the description must carry full behavioral disclosure. It fails to specify whether this is a partial update (omitted fields preserved) or destructive replacement, does not mention side effects, and lacks any mention of success/failure indicators or rate limiting.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

At only six words, the description is under-specified rather than appropriately concise. It fails to meet the richness threshold required for a mutation tool with multiple parameters, lacking front-loaded critical details about scope or behavior.

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?

For a mutation operation with three parameters and zero annotations or output schema, the description is inadequate. It should clarify the updatable attributes, behavioral side effects, and distinguish its scope from related tools in the sibling list.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, requiring the description to compensate by explaining the updatable fields. While it mentions 'settings' generally, it does not enumerate the specific settings available (name, php_version) or explain their expected formats (e.g., PHP version syntax), leaving critical semantic gaps.

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

Purpose3/5

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

States the basic action (update) and target (site settings) but lacks specificity about which settings can be modified. Fails to differentiate from sibling tools like pressable_set_php_version and pressable_set_site_usage_limits that appear to overlap in functionality.

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 general update tool versus the more specific 'set_' prefixed siblings (e.g., pressable_set_php_version). No mention of prerequisites, required permissions, or update semantics (partial vs full replacement).

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