Skip to main content
Glama
PCWProps

Pressable MCP Server

by PCWProps
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript

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

  • tools/collaborators.js:13-16 (handler)
    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);
}
  • tools/collaborators.js:4-17 (registration)
    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);
    }
},

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. 'List' clearly implies a read-only operation, but it does not disclose response format, pagination, or permission requirements. This is minimal but acceptable for a simple list tool.

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 that is front-loaded with the action and resource, with zero wasted words. It is appropriately concise and well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read-only list tool with one optional parameter and no output schema, this description is adequate. It states the purpose and the optional scope, but could be slightly more complete by explicitly mentioning account-level vs site-level selection via site_id.

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 schema already covers the only parameter (site_id) with a clear description. The tool description reinforces this by mentioning 'specific site', but adds little beyond the schema. Baseline of 3 is appropriate given 100% schema coverage.

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 uses a specific verb ('List') and resource ('collaborators'), and clearly scopes to 'account or specific site', distinguishing it from sibling tools like pressable_add_collaborator and other list tools.

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

Usage Guidelines4/5

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

The description clearly states when to use the tool: to list collaborators for an account or a specific site. It does not explicitly mention alternatives or exclusions, but the optional site_id implies filtering, providing adequate context for a simple list operation.

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