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

namecheap-webui-mcp

by Microck
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

namecheap_webui_import_cookies

Import cookies from a logged-in browser session to authenticate Namecheap web dashboard access, enabling account management without API keys.

Instructions

Import cookies from an existing logged-in browser session into the saved Namecheap auth state.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "namecheap_webui_import_cookies"
  }
}

Input Schema

NameRequiredDescriptionDefault
cookiesNoPlaywright-compatible cookies to import directly.
cookiesFilePathNoAbsolute path to a JSON cookie export file.
headedNoRun with a visible browser window.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations provided, and description does not disclose whether import replaces or merges cookies, any prerequisites, or side effects. Minimal behavioral insight beyond 'imports'.

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 is concise and front-loads the purpose. However, it could benefit from additional structure or notes.

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 3 parameters and no output schema or annotations, the description lacks completeness. It omits details about import behavior, success/failure signals, and prerequisites.

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 100%, so the description adds no new meaning beyond the schema. Parameters are well-documented in schema; description does not enhance understanding.

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 imports cookies from a browser session into Namecheap auth state, using specific verb and resource. It distinguishes from sibling tools like login by specifying 'import from existing logged-in session'.

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

Usage Guidelines3/5

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

No explicit guidance on when to use this tool versus alternatives like namecheap_webui_login. Usage is implied by the purpose but lacks exclusions or context.

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