Skip to main content
Glama

dnsimple

by io.usefulapi

Create a zone record

dnsimple_create_zone_record

Create a new DNS record in a zone. Additive — it adds a record without touching existing ones. API: POST /{account}/zones/{zone}/records.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ttlNoTime-to-live in seconds.
nameYesRecord name = the subdomain part WITHOUT the domain. Use "" (empty string) for the apex/root.
typeYesRecord type, e.g. A, AAAA, CNAME, MX, TXT, NS.
zoneYesZone name, e.g. example.com.
contentYesRecord content, e.g. an IP for A, a hostname for CNAME.
regionsNoRegions to publish the record in (e.g. ["global"]).
priorityNoPriority, for MX/SRV records.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare non-destructive, non-read-only. The description adds "additive" context, but fails to disclose return value, error conditions, authentication needs, or what happens on conflicts. Minimal added behavioral value.

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?

Two efficient sentences: first states purpose, second adds context and API endpoint. No wasted words, front-loaded.

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 no output schema and 7 parameters, the description lacks completeness. It does not specify return value, error scenarios, or prerequisites (e.g., zone ownership). For a creation tool, more is needed for agent to understand behavior fully.

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?

All 7 parameters have descriptions in the schema (100% coverage), so baseline is 3. The description does not add any parameter-specific details 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 it creates a new DNS record in a zone with the verb "Create" and resource "zone record". It adds "additive" to distinguish from updates, helping differentiation from siblings like update_zone_record.

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 (additive, no touching existing), but does not explicitly state when to use versus alternatives (e.g., update or delete) or provide exclusions. The additive comment offers modest guidance.

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

All dnsimple toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation5/5

Each tool targets a distinct resource and action (domain check, get, list, prices; zone record CRUD; contacts; zones; whoami). No overlapping purposes, and descriptions clearly differentiate them.

Naming Consistency5/5

All tools follow a consistent pattern: dnsimple_<verb>_<noun> (e.g., dnsimple_check_domain, dnsimple_list_zone_records). No mixing of conventions.

Tool Count5/5

12 tools cover essential domain management and DNS record operations without being excessive or too sparse. The scope aligns well with typical DNS provider functionality.

Completeness4/5

Covers core domain lookups, zone record CRUD, and account info. Missing domain registration, renewal, or transfer tools, but the server focuses on managing existing resources, so the gap is minor.

Resources