Skip to main content
Glama
PCWProps

Pressable MCP Server

by PCWProps

pressable_create_bash_bookmark

Create and save Bash or WP-CLI command bookmarks for WordPress site management through the Pressable API, enabling quick access to frequently used commands.

Instructions

Create a new Bash/WP-CLI command bookmark.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
descriptionNo
commandYes
command_typeYes

Implementation Reference

  • The handler function for 'pressable_create_bash_bookmark' that makes a POST request to the API to create a new bookmark.
    handler: async (args) => {
        return await api.post('/bash_command_bookmarks', { bash_command_bookmark: args });
    }
  • The input schema defining the required parameters (name, command, command_type) for the 'pressable_create_bash_bookmark' tool.
    inputSchema: {
        type: 'object',
        properties: {
            name: { type: 'string' },
            description: { type: 'string' },
            command: { type: 'string' },
            command_type: { type: 'string', enum: ['bash', 'wp_cli'] }
        },
        required: ['name', 'command', 'command_type']
    },
  • The registration block for the 'pressable_create_bash_bookmark' tool within the bookmarkTools array.
    {
        name: 'pressable_create_bash_bookmark',
        description: 'Create a new Bash/WP-CLI command bookmark.',
        inputSchema: {
            type: 'object',
            properties: {
                name: { type: 'string' },
                description: { type: 'string' },
                command: { type: 'string' },
                command_type: { type: 'string', enum: ['bash', 'wp_cli'] }
            },
            required: ['name', 'command', 'command_type']
        },
        handler: async (args) => {
            return await api.post('/bash_command_bookmarks', { bash_command_bookmark: args });
        }
    },
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 behavioral disclosure but fails to deliver. It does not state whether creation overwrites existing bookmarks, what permissions are required, what the tool returns upon success, or whether this operation has any side effects beyond creating the record.

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 single sentence is efficient and unambiguous, with no wasted words. However, given the lack of supporting schema documentation and annotations, this brevity results in insufficient information transfer rather than praiseworthy conciseness.

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 4-parameter mutation tool with no annotations, no output schema, and zero schema descriptions, the description is inadequate. It fails to explain what constitutes a bookmark, how it will be used later, or what validation rules apply to the inputs.

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?

With 0% schema description coverage, the description must compensate by explaining the four parameters, but it does not. While 'Bash/WP-CLI command' hints at the command and command_type parameters, it offers no guidance on the distinction between name (required identifier) and description (optional context), nor the expected format for command strings.

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 the specific verb 'Create' and identifies the resource as a 'Bash/WP-CLI command bookmark.' It effectively distinguishes this mutation operation from sibling read operations like pressable_get_bash_bookmark and pressable_list_bash_bookmarks, though it could better clarify the difference from execution tools like pressable_run_bash_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 no guidance on when to use this tool versus alternatives. It does not explain that bookmarks are for saving reusable commands versus immediate execution via the run_* tools, nor does it mention prerequisites like whether a bookmark name must be unique.

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