Skip to main content
Glama
PCWProps

Pressable MCP Server

by PCWProps

pressable_list_mu_plugins

Retrieve must-use WordPress plugins for Pressable-hosted sites to manage essential functionality and automate site administration tasks.

Instructions

Get a list of must-use (MU) plugins for your account/sites.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo
per_pageNo

Implementation Reference

  • The handler function that executes the 'pressable_list_mu_plugins' tool by calling the API.
    handler: async (args) => {
        return await api.get('/mu-plugins', args);
    }
  • Input schema validation for the 'pressable_list_mu_plugins' tool.
    inputSchema: {
        type: 'object',
        properties: {
            page: { type: 'integer' },
            per_page: { type: 'integer' }
        }
    },
  • Registration object for the 'pressable_list_mu_plugins' tool.
    {
        name: 'pressable_list_mu_plugins',
        description: 'Get a list of must-use (MU) plugins for your account/sites.',
        inputSchema: {
            type: 'object',
            properties: {
                page: { type: 'integer' },
                per_page: { type: 'integer' }
            }
        },
        handler: async (args) => {
            return await api.get('/mu-plugins', args);
        }
    },
Behavior2/5

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It fails to mention that results are paginated (despite having page/per_page parameters), does not describe the return format, and omits safety characteristics (read-only nature).

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

Conciseness3/5

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

Single sentence is appropriately concise, but given the lack of annotations, zero schema coverage, and no output schema, this brevity leaves critical information gaps rather than earning its place through information density.

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?

With zero annotations, zero schema coverage, no output schema, and multiple sibling tools with similar purposes, the description provides insufficient context. It omits pagination behavior, MU plugin characteristics, and response structure necessary for correct invocation.

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 description coverage is 0% (page and per_page are undocumented in schema), yet the description adds no information about these pagination parameters or their expected values. Complete failure to compensate for the schema gap.

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 clearly identifies the resource as 'must-use (MU) plugins', distinguishing it from sibling pressable_list_plugins (regular plugins) by specifying the MU type. However, it fails to clarify the distinction from pressable_get_mu_plugin (singular retrieval).

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?

Provides no guidance on when to use this tool versus alternatives like pressable_get_mu_plugin or pressable_list_plugins. Does not explain that MU plugins are automatically active WordPress plugins managed at the site level, which would help users determine relevance.

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