Skip to main content
Glama
Sign In
Akamai Cloud MCP Server

Akamai Cloud MCP Server

Official
by akamai-developers
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

linode_list_domain_records

Read-only

Retrieve all DNS records for a specified domain, including A, AAAA, NS, MX, CNAME, TXT, SRV, PTR, and CAA types with their name, target, TTL, and priority/weight/port values.

Instructions

List the DNS records for a domain (A, AAAA, NS, MX, CNAME, TXT, SRV, PTR, CAA), with name, target, TTL, and priority/weight/port where set.

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_id": "<domain_id>"
    },
    "name": "linode_list_domain_records"
  }
}

Input Schema

NameRequiredDescriptionDefault
domain_idYes
detailNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

The annotation indicates readOnlyHint=true, and the description adds value by detailing the returned fields (name, target, TTL, priority/weight/port). No contradictions with annotations.

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, front-loaded sentence with no wasted words. It efficiently conveys purpose and scope.

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?

Given the presence of an output schema, the description adequately covers what the tool does and the key fields. It does not mention pagination or ordering, but these may be in the output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description does not explain the parameters (domain_id, detail) beyond implying domain_id is needed. The detail parameter's behavior (concise vs full) is left unspecified.

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 lists DNS records for a domain, enumerating specific record types and fields returned. It distinguishes from siblings like linode_list_domains which lists domains themselves.

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 use when needing DNS records of a domain, but does not explicitly state when to use vs alternatives like linode_get_domain or linode_list_domains. No exclusions or when-not guidance 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

Other Tools