Skip to main content
Glama
PCWProps

Pressable MCP Server

by PCWProps
OverviewSchemaRelated ServersScoreDiscussions
JavaScript

pressable_install_plugin

Install and activate WordPress plugins on Pressable sites using the plugin slug from WordPress.org to extend site functionality.

Instructions

Install and activate a plugin on a site.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
plugin_slugYesSlug of the plugin from WP.org

Implementation Reference

  • tools/content.js:27-29 (handler)
    Handler for pressable_install_plugin, which performs a POST request to install a plugin.
    handler: async (args) => {
    return await api.post(`/sites/${args.id}/plugins`, { plugins: [args.plugin_slug] });
}
  • tools/content.js:19-26 (schema)
    Input schema for pressable_install_plugin tool.
    inputSchema: {
    type: 'object',
    properties: {
        id: { type: 'string' },
        plugin_slug: { type: 'string', description: 'Slug of the plugin from WP.org' }
    },
    required: ['id', 'plugin_slug']
},
  • tools/content.js:16-30 (registration)
    Registration of pressable_install_plugin within the tools array.
    {
    name: 'pressable_install_plugin',
    description: 'Install and activate a plugin on a site.',
    inputSchema: {
        type: 'object',
        properties: {
            id: { type: 'string' },
            plugin_slug: { type: 'string', description: 'Slug of the plugin from WP.org' }
        },
        required: ['id', 'plugin_slug']
    },
    handler: async (args) => {
        return await api.post(`/sites/${args.id}/plugins`, { plugins: [args.plugin_slug] });
    }
},

Tool Definition Quality

B3.3/5.0
Behavior3/5

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

Without annotations, the description must carry the full burden. It discloses the compound nature of the operation (install AND activate), implying write access. However, it omits critical behavioral details: failure modes if the plugin exists, whether this is idempotent, permission requirements, and side effects.

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

Conciseness5/5

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

The single sentence is appropriately sized, front-loaded with the action, and contains no redundancy. Every word earns its place.

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

Completeness3/5

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

For a 2-parameter mutation tool with no annotations or output schema, the description meets minimum viability. However, it lacks necessary completeness for a write operation: no return value description, no error handling disclosure, and incomplete parameter documentation for the 'id' field.

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?

With 50% schema coverage (only 'plugin_slug' is described), the baseline is 3. The description mentions 'on a site,' implying the 'id' parameter refers to a site ID, but provides no format guidance or clarification that this is a Pressable site identifier rather than URL or name.

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 clear verbs ('Install and activate') and identifies the resource ('plugin') and scope ('on a site'). It effectively conveys the dual-action nature of the operation, though it assumes WordPress/Pressable context rather than stating it explicitly.

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 like 'pressable_list_plugins', prerequisites for installation, or error conditions (e.g., plugin already installed).

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