Skip to main content
Glama
PCWProps

Pressable MCP Server

by PCWProps
OverviewSchemaRelated ServersScoreDiscussions
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`);
    }
},

Tool Definition Quality

C2.7/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden of behavioral disclosure but provides none. It does not indicate whether the operation is read-only (implied by 'Get' but not explicit), safe to retry, or what happens if the site ID is invalid.

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 single-sentence description is appropriately brief at 9 words, but with zero schema documentation and no output schema, this brevity constitutes under-documentation rather than efficient communication.

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?

Given zero schema descriptions, no annotations, and no output schema, the description provides insufficient context. It omits: the specific identity of the 'id' parameter, expected return structure, pagination behavior, and relationship to plugin management workflows.

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 0% and the description fails to adequately compensate. While 'for a specific site' hints that the 'id' parameter refers to a site identifier, it does not explicitly define this mapping or indicate required format/validation rules.

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 a specific verb ('Get') and resource ('list of plugins') with clear scope ('for a specific site'). However, it fails to explicitly distinguish from sibling tool `pressable_list_mu_plugins` (must-use plugins) or indicate whether these are installed/active plugins.

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 (e.g., `pressable_get_site` to verify site existence first, or `pressable_list_mu_plugins` for must-use plugins), nor prerequisites for obtaining the site ID.

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