Skip to main content
Glama
PCWProps

Pressable MCP Server

by PCWProps

pressable_list_bash_bookmarks

Retrieve and search through saved Bash command bookmarks for managing WordPress sites via the Pressable API.

Instructions

Get a list of Bash command bookmarks for your account.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
searchNoSearch term for name or command
per_pageNo
pageNo

Implementation Reference

  • The handler function that executes the 'pressable_list_bash_bookmarks' tool by making an API call.
    handler: async (args) => {
        return await api.get('/bash_command_bookmarks', args);
    }
  • The input schema defining the arguments for 'pressable_list_bash_bookmarks'.
    inputSchema: {
        type: 'object',
        properties: {
            search: { type: 'string', description: 'Search term for name or command' },
            per_page: { type: 'integer' },
            page: { type: 'integer' }
        }
    },
  • The tool definition for 'pressable_list_bash_bookmarks' within the bookmarkTools array.
    {
        name: 'pressable_list_bash_bookmarks',
        description: 'Get a list of Bash command bookmarks for your account.',
        inputSchema: {
            type: 'object',
            properties: {
                search: { type: 'string', description: 'Search term for name or command' },
                per_page: { type: 'integer' },
                page: { type: 'integer' }
            }
        },
        handler: async (args) => {
            return await api.get('/bash_command_bookmarks', args);
        }
    },
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It indicates a read operation via 'Get', but fails to mention pagination behavior, rate limits, or the distinction between this and the singular 'get_bash_bookmark' sibling. The safety profile (read-only) is only implied, not stated.

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?

Single sentence of nine words is appropriately front-loaded and efficient. However, given the gaps in schema coverage and lack of output schema, this brevity results in underspecification rather than effective 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?

Incomplete given the low schema coverage, absence of output schema, and existence of closely related sibling tools. The description should explain the list semantics, mention the search functionality, and clarify the pagination model to be complete.

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 only 33% (only 'search' is described; 'per_page' and 'page' lack descriptions). With low coverage, the description must compensate by explaining pagination, but it mentions no parameters at all, leaving the pagination controls undocumented.

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 specific verb 'Get' and resource 'Bash command bookmarks' with scope 'for your account'. It implicitly distinguishes from sibling 'pressable_get_bash_bookmark' via the word 'list', though it doesn't explicitly clarify when to use this versus the singular fetch variant.

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?

No guidance provided on when to use this tool versus alternatives, pagination strategies, or search syntax. The description only states what the tool does, not when to invoke it or how to handle the paginated results.

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