Skip to main content
Glama
PCWProps

Pressable MCP Server

by PCWProps

pressable_run_wp_cli

Execute WP-CLI commands on WordPress sites through the Pressable MCP Server to manage plugins, clear cache, and perform administrative tasks.

Instructions

Run WP-CLI commands on a specific site. Commands are prefixed with "wp" automatically.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
commandsYesList of WP-CLI commands (e.g., ["plugin list", "cache flush"])

Implementation Reference

  • The handler function for 'pressable_run_wp_cli' that executes the WP-CLI commands via the API.
    handler: async (args) => {
        return await api.post(`/sites/${args.id}/wordpress/wpcli`, { commands: args.commands });
    }
  • The input schema defining the required 'id' and 'commands' parameters for 'pressable_run_wp_cli'.
    inputSchema: {
        type: 'object',
        properties: {
            id: { type: 'string' },
            commands: {
                type: 'array',
                items: { type: 'string' },
                description: 'List of WP-CLI commands (e.g., ["plugin list", "cache flush"])'
            }
        },
        required: ['id', 'commands']
    },
  • The full tool definition and registration for 'pressable_run_wp_cli'.
    {
        name: 'pressable_run_wp_cli',
        description: 'Run WP-CLI commands on a specific site. Commands are prefixed with "wp" automatically.',
        inputSchema: {
            type: 'object',
            properties: {
                id: { type: 'string' },
                commands: {
                    type: 'array',
                    items: { type: 'string' },
                    description: 'List of WP-CLI commands (e.g., ["plugin list", "cache flush"])'
                }
            },
            required: ['id', 'commands']
        },
        handler: async (args) => {
            return await api.post(`/sites/${args.id}/wordpress/wpcli`, { commands: args.commands });
        }
    },
Behavior3/5

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

No annotations provided, so description carries full burden. Valuably discloses that commands are auto-prefixed with 'wp', preventing user error. However, missing critical safety disclosure: WP-CLI can be destructive (delete content, drop tables), and description doesn't mention output format, permissions required, or execution environment constraints.

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?

Two sentences, zero waste. First sentence establishes purpose; second sentence provides essential behavioral constraint (auto-prefixing). Appropriately front-loaded with no filler.

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?

Command execution tools are high-risk operations with potential for data destruction. Without annotations or output schema, the description should disclose risks, failure modes, or required privileges. Currently insufficient for safe autonomous use given the stakes.

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

Parameters4/5

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

Schema coverage is 50% (id undocumented). Description adds crucial semantic detail not in schema: commands are auto-prefixed with 'wp'. Also implies 'id' refers to a site identifier via 'specific site'. However, 'id' parameter receives no explicit documentation (format, source, example values).

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 specific action (Run WP-CLI commands) and target (specific site). However, fails to differentiate from sibling tool pressable_run_bash_commands, which also executes commands on sites, leaving ambiguity about which to choose.

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 versus specialized siblings like pressable_install_plugin or pressable_list_wp_users, nor when to prefer pressable_run_bash_commands. No warnings about command safety or prerequisites.

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