porkbun-mcp-server

set_email_password

Update the password for an email hosting account by providing the full email address and new password.

Instructions

Set the password for an email hosting account. email_address is the full address (e.g. user@example.com).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "email_address": "<email_address>",
      "password": "<password>"
    },
    "name": "set_email_password"
  }
}

Input Schema

Name	Required	Description	Default
`password`	Yes
`email_address`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.5.0Jul 8, 2026

TDQS

B3.3/5.0

Behavior2/5

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

No annotations are present, and the description does not disclose behavioral details such as whether the password is overwritten, if there are policy constraints, or if authentication is required. The mutation nature is implied but not elaborated.

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 two concise sentences with no fluff. It front-loads the action and then clarifies the key parameter. Every sentence serves a purpose.

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?

For a simple two-parameter tool with no output schema, the description is adequate but lacks details on password requirements, side effects, or security implications. More context would improve completeness.

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 description adds meaning for the 'email_address' parameter by specifying it is the full address with an example. However, the 'password' parameter is not described, and schema coverage is 0%, so the description only partially compensates.

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 clearly states the action (Set the password) and the resource (email hosting account). It also clarifies the email_address parameter format with an example. This distinguishes it from sibling tools which are mostly about DNS, domains, and other operations.

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 is provided on when to use this tool versus alternatives, prerequisites, or conditions. Sibling tools like 'check_availability' or 'create_invite' are unrelated, but still no usage context is given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server