Skip to main content
Glama
PCWProps

Pressable MCP Server

by PCWProps

pressable_reset_wp_admin_password

Reset WordPress admin passwords for Pressable-hosted sites to regain access when credentials are lost or compromised.

Instructions

Reset the WordPress admin password for a site.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes

Implementation Reference

  • The handler for the 'pressable_reset_wp_admin_password' tool performs a POST request to the site's reset-password endpoint.
    handler: async (args) => {
        return await api.post(`/sites/${args.id}/reset-password`);
    }
  • The input schema for 'pressable_reset_wp_admin_password' expects an object with a site 'id'.
    inputSchema: {
        type: 'object',
        properties: { id: { type: 'string' } },
        required: ['id']
    },
  • tools/sites.js:136-147 (registration)
    Registration of the 'pressable_reset_wp_admin_password' tool within the siteTools array.
    {
        name: 'pressable_reset_wp_admin_password',
        description: 'Reset the WordPress admin password for a site.',
        inputSchema: {
            type: 'object',
            properties: { id: { type: 'string' } },
            required: ['id']
        },
        handler: async (args) => {
            return await api.post(`/sites/${args.id}/reset-password`);
        }
    },
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It fails to explain what happens during the reset (e.g., generates a temporary password, emails a link, sets a default value) or whether this invalidates existing sessions.

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?

Single sentence with no wasted words. However, extreme brevity results in insufficient detail for a security-sensitive mutation operation.

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 no annotations, no output schema, and a single undocumented parameter, the description inadequately covers a sensitive operation. It omits critical security context such as how the new password is delivered or whether the action is logged/irreversible.

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% for the single 'id' parameter. While the phrase 'for a site' implies the ID refers to a site identifier, the description does not explicitly document the parameter name, expected format, or confirm this mapping, leaving ambiguity between site ID and user ID.

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?

Description states a specific action (Reset) and resource (WordPress admin password for a site), which distinguishes it from sibling pressable_reset_sftp_user_password. However, it lacks specificity on which admin user is affected (primary, all, etc.) and what 'reset' entails.

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 provided on when to use this tool versus alternatives like pressable_run_wp_cli to manually update credentials, or what prerequisites exist (e.g., site ownership verification).

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