Skip to main content
Glama
PCWProps

Pressable MCP Server

by PCWProps

pressable_list_collaborators

View collaborators for Pressable WordPress accounts or sites to manage team access and permissions.

Instructions

List all collaborators for an account or specific site.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
site_idNoOptional site ID to filter by

Implementation Reference

  • The handler function for pressable_list_collaborators tool which fetches collaborators from the API.
    handler: async (args) => {
        const path = args.site_id ? `/sites/${args.site_id}/collaborators` : '/collaborators';
        return await api.get(path);
    }
  • The registration block for the pressable_list_collaborators tool.
    {
        name: 'pressable_list_collaborators',
        description: 'List all collaborators for an account or specific site.',
        inputSchema: {
            type: 'object',
            properties: {
                site_id: { type: 'string', description: 'Optional site ID to filter by' }
            }
        },
        handler: async (args) => {
            const path = args.site_id ? `/sites/${args.site_id}/collaborators` : '/collaborators';
            return await api.get(path);
        }
    },
Behavior2/5

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

No annotations provided, so description carries full burden. States 'List' operation but omits pagination behavior, return structure, collaborator field details, and rate limits. Minimal behavioral disclosure beyond basic scope.

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?

Single efficient sentence, front-loaded with action verb. No redundancy or structural waste.

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?

Adequate for a simple 1-parameter read tool with complete schema coverage. Absence of output schema and annotations creates gaps but is acceptable for this complexity level.

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?

Schema coverage is 100%, establishing baseline 3. Description adds contextual framing that parameter absence means 'account' scope while presence means 'specific site', adding semantic clarity beyond raw schema.

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?

Clear verb 'List' with resource 'collaborators' and scope 'account or specific site'. Loses a point for failing to explicitly differentiate from sibling tools like pressable_add_collaborator or clarify distinction from user-listing tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Implies usage pattern through 'account or specific site' phrasing (use without site_id for account-wide, with it for site-specific), but lacks explicit when-to-use guidance or mention of alternatives.

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