Skip to main content
Glama
PCWProps

Pressable MCP Server

by PCWProps
OverviewSchemaSourceRelated ServersDiscussionsAdmin
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] });
    }
},

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description carries full responsibility for behavioral disclosure. It states the action but does not describe potential side effects, required permissions, behavior on conflicts (e.g., already installed plugin), or any other important operational details.

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 description is a single, direct sentence with no wasted words. However, it may be under-specified for a tool with mutation side effects, so it is concise but lacks necessary elaboration.

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 state-changing tool with no annotations and no output schema, the description is too minimal. It leaves out important context about return values, error cases, and operational behavior, making it incomplete for reliable agent decision-making.

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 50% (plugin_slug has a description, id does not). The description does not clarify what 'id' refers to (presumably the site ID) and does not elaborate on the plugin_slug beyond the schema. It adds minimal semantic value.

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 ('Install and activate') and the resource ('a plugin on a site'), making the tool's purpose unambiguous. It is distinct from sibling tools like pressable_list_plugins, though it does not explicitly name alternatives or scope.

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 is provided on when to use this tool versus others. It does not mention prerequisites, exclusions, or alternative tools, leaving the agent to infer usage from the name and description.

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