Skip to main content
Glama
PCWProps

Pressable MCP Server

by PCWProps
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript

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

  • tools/automation.js:38-40 (handler)
    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 });
}
  • tools/automation.js:26-37 (schema)
    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']
},
  • tools/automation.js:23-41 (registration)
    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 });
    }
},

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.3/5.0
Behavior1/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 behavioral disclosure. It merely states that it runs bash commands on a site, but does not disclose important traits such as whether the commands are destructive, whether they require elevated permissions, how output is returned, or execution semantics (sequential vs parallel). This is a high-risk tool with zero added transparency.

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?

The description is a single concise sentence and is front-loaded with the core action. However, it is under-specified for a tool that executes arbitrary bash commands; the brevity is not a virtue when critical behavioral details are omitted. It is not wasteful but it is insufficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This tool is complex and potentially dangerous (running arbitrary bash commands on a site), with no annotations and no output schema. The description is severely incomplete: it does not mention expected outputs, side effects, prerequisites, or safety implications. It is only six words long and provides no contextual grounding.

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 coverage is 50% (only 'commands' has a description, 'id' does not). The description text adds no meaning beyond the schema: it does not explain that 'id' is likely the site ID or how the command array is processed. The command description 'List of Bash commands' is trivial and does not clarify execution order or error handling.

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 clearly states the action ('Run Bash commands') and the resource ('a specific site'), which is a specific verb+resource combination. However, it does not explicitly distinguish itself from the sibling tool 'pressable_run_wp_cli', so it lacks explicit sibling differentiation.

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 gives no guidance on when to use this tool versus alternatives like 'pressable_run_wp_cli' or 'pressable_list_bash_bookmarks'. It does not indicate prerequisites, exclusions, or typical use cases, leaving the agent to infer appropriate usage.

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