Skip to main content
Glama
PCWProps

Pressable MCP Server

by PCWProps
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript

pressable_list_plugins

Retrieve a list of plugins installed on a WordPress site to manage and audit site functionality.

Instructions

Get a list of plugins for a specific site.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes

Implementation Reference

  • tools/content.js:12-14 (handler)
    The handler for the 'pressable_list_plugins' tool that fetches plugins from the API.
    handler: async (args) => {
    return await api.get(`/sites/${args.id}/plugins`);
}
  • tools/content.js:4-15 (registration)
    The full registration object for the 'pressable_list_plugins' tool, including the schema and handler definition.
    {
    name: 'pressable_list_plugins',
    description: 'Get a list of plugins for a specific site.',
    inputSchema: {
        type: 'object',
        properties: { id: { type: 'string' } },
        required: ['id']
    },
    handler: async (args) => {
        return await api.get(`/sites/${args.id}/plugins`);
    }
},

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

There are no annotations, so the description must fully convey behavioral traits. The verb 'Get' implies a read-only operation, but the description does not explicitly state this, nor does it disclose any permissions, potential errors, or return behavior beyond the basic listing.

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 description is a single sentence of nine words, delivering the core purpose without any unnecessary content. It is concise and front-loaded.

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 simple list tool with one parameter and no output schema, the description covers the basic purpose but lacks detail on the return structure, potential edge cases, or prerequisites. It is minimally adequate but not complete for an agent to fully anticipate the tool's behavior.

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?

The input schema has one required 'id' parameter with no description, while the tool description says 'for a specific site', indirectly suggesting that 'id' is the site ID. This partially compensates for the lack of schema coverage, but the description does not specify the format or expected values for the parameter.

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 clearly states the action 'Get' and the resource 'list of plugins for a specific site', which distinguishes it from sibling tools like list_themes or list_mu_plugins. It is specific and unambiguous.

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 mention any conditions, prerequisites, or alternative tools, despite there being several similar list tools in the sibling set.

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