Skip to main content
Glama
PCWProps

Pressable MCP Server

by PCWProps
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript

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

  • tools/bookmarks.js:32-34 (handler)
    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 });
}
  • tools/bookmarks.js:22-31 (schema)
    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']
},
  • tools/bookmarks.js:19-35 (registration)
    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 });
    }
},

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 full responsibility for behavioral disclosure. It merely restates the action ('Create') without mentioning side effects, permission requirements, duplicate handling, or idempotency. It adds no information beyond what the tool name already implies.

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?

The description is a single short sentence, but it is under-specified. It does not earn its place because it is effectively a tautology of the tool name. True conciseness would deliver the necessary information in an efficient manner; this simply omits it.

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?

Given the tool has 4 parameters, no output schema, no annotations, and 48 sibling tools, the description is severely incomplete. It does not explain what a bookmark is for, the meaning of command_type, or the expected behavior after creation. The agent is left without critical context for correct invocation.

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

Parameters1/5

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

Schema description coverage is 0%. The description does not explain any of the four parameters (name, command, description, command_type), the enum choices (bash vs wp_cli), or how they relate to each other. It fails to add value beyond the raw schema.

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

Purpose5/5

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

The description uses a specific verb ('Create') and clearly identifies the resource ('Bash/WP-CLI command bookmark'). This distinguishes it from sibling tools like pressable_list_bash_bookmarks and pressable_get_bash_bookmark, which are read operations.

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 explicit guidance on when to use this tool versus alternatives. It does not mention that this is for storing recurring commands or that running commands directly is possible via pressable_run_bash_commands or pressable_run_wp_cli. Usage is only implied by the action itself.

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