namecheap-mcp

Reactivate an expired domain (PAID)

reactivate_domain

Destructive

Reactivate an expired domain that is still within Namecheap's redemption/grace window. Confirm the paid reactivation; use renew_domain for domains that have not expired.

Instructions

Reactivate a domain that has EXPIRED but is still within Namecheap's redemption/grace window. THIS SPENDS MONEY (reactivation can cost more than a normal renewal) and needs confirm=true. For domains that have not yet expired, use renew_domain.

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": {
      "domain": "<domain>"
    },
    "name": "reactivate_domain"
  }
}

Input Schema

Name	Required	Description
`domain`	Yes
`confirm`	No	Must be true to place the paid reactivation.
`promotionCode`	No

Output Schema

Name	Required	Description	Default
`domain`	No
`account`	Yes
`orderId`	No
`provider`	Yes
`environment`	No
`reactivated`	Yes
`chargedAmount`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Aug 11, 2026

TDQS

A4.7/5.0

Behavior5/5

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

The description adds crucial behavioral context beyond the annotations: it warns that the operation spends money and can cost more than a normal renewal, and explicitly states confirm=true is required. This aligns with readOnlyHint=false and destructiveHint=true, with no contradiction.

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 sentences, front-loaded with the core purpose, then the critical cost warning and alternative. Every sentence adds essential information without redundancy.

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

Completeness5/5

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

For a paid, potentially expensive operation, the description covers the eligibility window, cost implication, required confirmation, and provides a clear alternative. The output schema exists, so return values need not be described. This is comprehensive for the tool's complexity.

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 description coverage is low (33%). The description explains the confirm parameter's role (must be true) and implicitly that domain is the target, but provides no additional detail for domain format or promotionCode. It partially compensates for the low coverage but leaves promotionCode's purpose unclear.

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 tool's function: reactivating expired domains within Namecheap's redemption/grace window. It uses a specific verb and resource, and explicitly distinguishes from renew_domain for non-expired domains.

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

Usage Guidelines5/5

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

The description explicitly says when to use this tool (expired domains within the redemption/grace window) and when to use an alternative ('For domains that have not yet expired, use renew_domain.'). This provides clear usage guidance with an exclusion.

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