Skip to main content
Glama
PCWProps

Pressable MCP Server

by PCWProps

pressable_add_collaborator

Add a collaborator to a WordPress site by specifying the site ID and collaborator email address.

Instructions

Add a collaborator to a site.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
site_idYes
emailYes

Implementation Reference

  • The handler function for 'pressable_add_collaborator' which calls the API to add a collaborator to a site.
    handler: async (args) => {
        return await api.post(`/sites/${args.site_id}/collaborators`, { email: args.email });
    }
  • The input schema for 'pressable_add_collaborator' defining site_id and email as required arguments.
    inputSchema: {
        type: 'object',
        properties: {
            site_id: { type: 'string' },
            email: { type: 'string' }
        },
        required: ['site_id', 'email']
    },
  • The registration block for the 'pressable_add_collaborator' tool.
        {
            name: 'pressable_add_collaborator',
            description: 'Add a collaborator to a site.',
            inputSchema: {
                type: 'object',
                properties: {
                    site_id: { type: 'string' },
                    email: { type: 'string' }
                },
                required: ['site_id', 'email']
            },
            handler: async (args) => {
                return await api.post(`/sites/${args.site_id}/collaborators`, { email: args.email });
            }
        }
    ];
Behavior2/5

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

Zero annotations provided, yet description discloses no behavioral traits: whether an email invitation is sent, what access level is granted, if the operation is idempotent, or error conditions (e.g., if email already has access).

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?

Extremely concise (5 words) but underspecified given the lack of annotations and schema coverage. No redundancy, but insufficient content for the tool's complexity.

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?

Incomplete for a collaboration-invitation tool with no output schema and undocumented parameters. Should describe the invitation flow, returned confirmation, or side effects (emails sent, account creation).

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% (both parameters undocumented). Description mentions 'site' and 'collaborator' conceptually but does not map these to `site_id` (format? UUID? slug?) or `email` (collaborator's email vs. inviter's?). Fails to compensate for missing schema documentation.

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 (Add) + resource (collaborator) + target (site). Distinguishes adequately from sibling `list_collaborators` and other site-management tools. However, lacks scope clarification regarding what permissions/role the collaborator receives.

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 on when to use versus alternatives, prerequisites (e.g., does the collaborator need an existing account?), or expected outcomes. No mention of checking existing collaborators before adding.

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