Skip to main content
Glama
Sign In
namecheap-webui-mcp

namecheap-webui-mcp

by Microck
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

namecheap_dns_set_records

Manage DNS records for a domain by appending or replacing host entries like A, CNAME, TXT, MX, and AAAA records.

Instructions

Append or replace host records in the Advanced DNS page for a 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": {
      "domainName": "<domainName>",
      "records": "<records>"
    },
    "name": "namecheap_dns_set_records"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainNameYesFull domain name, for example example.com
modeNoAppend new records or replace the existing host records.append
headedNoRun with a visible browser window.
recordsYesThe DNS records to create in the web UI.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavior. It mentions operating in the Advanced DNS page and implies a browser UI (via the 'headed' parameter), but it does not warn about destructive potential (replacing all records), required authentication, or that it imports cookies first. The safety profile is unclear.

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?

The description is a single, concise sentence that front-loads the core action. No wasted words, but it omits important behavioral details. Efficiency is high, but completeness suffers.

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?

Given no output schema, the description should hint at return values or success criteria, but it does not. It also lacks integration context with sibling tools (e.g., must call login first). The tool modifies DNS records, which could have side effects, but these are unmentioned.

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 input schema already describes all 4 parameters with 100% coverage, including details like enumerations for mode and record fields. The description adds little beyond stating modes 'append' or 'replace', so it meets the baseline but does not improve understanding beyond the schema.

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 appends or replaces host records in the Advanced DNS page. It uses specific verbs (append/replace) and identifies the resource (host records), distinguishing it from sibling tools like get_records or set_nameservers.

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?

The description does not provide guidance on when to use this tool versus alternatives, nor does it mention prerequisites like needing to import cookies or being logged into the Namecheap dashboard. Sibling tools such as get_records and set_nameservers are listed but not contrasted.

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