Skip to main content
Glama
PCWProps

Pressable MCP Server

by PCWProps

pressable_run_bash_commands

Execute Bash commands on a WordPress site to automate server operations, manage configurations, or perform maintenance tasks directly through the Pressable API.

Instructions

Run Bash commands on a specific site.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
commandsYesList of Bash commands

Implementation Reference

  • The handler for the 'pressable_run_bash_commands' tool, which performs an API request to execute bash commands.
    handler: async (args) => {
        return await api.post(`/sites/${args.id}/wordpress/commands`, { commands: args.commands });
    }
  • Input schema definition for the 'pressable_run_bash_commands' tool.
    inputSchema: {
        type: 'object',
        properties: {
            id: { type: 'string' },
            commands: {
                type: 'array',
                items: { type: 'string' },
                description: 'List of Bash commands'
            }
        },
        required: ['id', 'commands']
    },
  • Registration of the 'pressable_run_bash_commands' tool.
    {
        name: 'pressable_run_bash_commands',
        description: 'Run Bash commands on a specific site.',
        inputSchema: {
            type: 'object',
            properties: {
                id: { type: 'string' },
                commands: {
                    type: 'array',
                    items: { type: 'string' },
                    description: 'List of Bash commands'
                }
            },
            required: ['id', 'commands']
        },
        handler: async (args) => {
            return await api.post(`/sites/${args.id}/wordpress/commands`, { commands: args.commands });
        }
    },
Behavior2/5

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

With no annotations provided, the description carries the full burden of disclosure but fails to mention critical behavioral traits: it does not warn that bash commands can be destructive, does not describe the execution environment (e.g., working directory, user permissions, sandboxing), timeout behavior, or what output format to expect.

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

Conciseness4/5

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

The description is extremely concise at six words with the action front-loaded. While efficient, it is arguably under-specified for a high-risk tool, though it contains no wasted words or redundant phrases.

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 tool enabling arbitrary code execution with no output schema, partial parameter documentation, and no annotations, the description is dangerously incomplete. It lacks necessary safety warnings, execution context, and return value information required for safe and effective invocation.

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?

Schema coverage is 50% (only `commands` is described in schema as 'List of Bash commands'). The description implies `id` refers to a site ('on a specific site'), providing minimal context for the undocumented parameter, but does not fully compensate for the missing schema documentation by explaining parameter formats, constraints, or providing examples.

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?

The description uses a specific verb ('Run') and identifies the resource ('Bash commands' on a 'specific site'), making the basic purpose clear. However, it fails to distinguish from the sibling tool `pressable_run_wp_cli`, which could cause confusion about when to use arbitrary shell commands versus WordPress-specific CLI commands.

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 absolutely no guidance on when to use this tool versus alternatives (like `run_wp_cli`), prerequisites (such as necessary permissions), or warnings about appropriate use cases. For a tool capable of arbitrary command execution, this lack of guardrails is a significant gap.

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