Skip to main content
Glama
PCWProps

Pressable MCP Server

by PCWProps

pressable_list_wp_users

Retrieve a list of WordPress users for a specific Pressable site to manage access and permissions.

Instructions

List WordPress users for a specific site.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
pageNo
per_pageNo

Implementation Reference

  • The tool 'pressable_list_wp_users' is defined in 'tools/content.js'. It includes the tool name, description, input schema, and the handler function that calls the Pressable API to list WordPress users for a given site.
        name: 'pressable_list_wp_users',
        description: 'List WordPress users for a specific site.',
        inputSchema: {
            type: 'object',
            properties: {
                id: { type: 'string' },
                page: { type: 'integer' },
                per_page: { type: 'integer' }
            },
            required: ['id']
        },
        handler: async (args) => {
            const { id, ...params} = args;
            return await api.get(`/sites/${id}/wordpress/users`, params);
        }
    }
Behavior2/5

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

No annotations provided, so description carries full disclosure burden. 'List' implies read-only but doesn't confirm safety, rate limits, or return format. Omits critical list behavior: pagination semantics, maximum `per_page` values, or total count availability.

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?

Six words with zero redundancy. However, brevity is excessive given zero schema descriptions—lacks front-loaded parameter hints that would prevent agent hallucination.

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?

Inadequate for a 3-parameter list operation with no output schema and zero parameter descriptions. Missing: pagination behavior explanation, `id` format requirements, and return structure. Should explicitly state this wraps the WordPress REST API users endpoint.

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 0% schema coverage, description minimally compensates by implying `id` is a site identifier ('for a specific site'). However, completely omits `page` and `per_page` pagination semantics, leaving two-thirds of parameters undocumented.

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?

States specific verb (List) and resource (WordPress users) with scope (for a specific site). Distinguishes from siblings like `pressable_get_sftp_users` and `pressable_list_collaborators` by specifying 'WordPress users', though could clarify relationship to site collaborators.

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 versus `pressable_list_collaborators` or `pressable_get_sftp_users`. No mention of prerequisites (site ID requirement) or when pagination is necessary.

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