vercel-mcp-pro

get_domain_config

Retrieve the DNS records and verification settings required by Vercel to configure a domain. Use this to set up domain ownership verification at your registrar.

Instructions

Get the DNS/verification configuration Vercel expects for a domain (records to set at your registrar).

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": "get_domain_config"
  }
}

Input Schema

Name	Required	Description
`domain`	Yes	Domain name.
`teamId`	No	Team ID to scope the request. Falls back to VERCEL_TEAM_ID when omitted.
`slug`	No	Team slug to scope the request (alternative to teamId).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 11, 2026

TDQS

A3.6/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden. It describes a read operation but does not explicitly state lack of side effects, authentication requirements, or rate limits. The phrase 'records to set' implies no modification, but details are sparse.

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 a single sentence of 17 words, front-loaded with the verb 'Get'. No redundant or extraneous information.

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

Completeness4/5

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

Although there is no output schema, the description gives a clear indication of what the tool returns (DNS records to set). For a simple get operation with well-documented parameters, this is nearly complete, though the exact response format is not described.

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 has 100% description coverage, so the schema already documents all three parameters. The description does not add extra meaning beyond what the schema provides, meeting the baseline of 3.

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 retrieves the DNS/verification configuration for a domain, specifically the records to set. The verb 'Get' and resource are explicit, distinguishing it from sibling tools like get_domain or verify_domain.

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?

The description implies usage when you need to know DNS records to set, but it lacks explicit guidance on when to use this tool versus alternatives or when not to use it. No sibling differentiation is provided.

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

Deploy Server