Skip to main content
Glama
Sign In
AWS MCP Server

AWS MCP Server

by marcelobrake
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

aws_route53_list_hosted_zones

List AWS Route 53 hosted zones to view DNS domains managed by your account, enabling domain inventory management and configuration verification.

Instructions

List Route53 hosted zones (DNS domains managed by this account).

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

Input Schema

NameRequiredDescriptionDefault
profileNoAWS profile name from ~/.aws/config (e.g., 'default', 'production')
regionNoAWS region override (e.g., 'us-east-1', 'sa-east-1')
max_itemsNoMaximum zones to return (as string)

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?

With no annotations provided, the description carries the full burden of behavioral disclosure but only explains the operation purpose, not behavioral traits. It fails to explicitly state this is a safe read-only operation, describe pagination behavior, or explain that 'max_items' accepts string values (an AWS API quirk).

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, efficiently structured sentence with no wasted words. The parenthetical clarification '(DNS domains managed by this account)' adds immediate value and scope definition without clutter.

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

Completeness3/5

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

For a straightforward enumeration tool with full schema coverage, the description adequately identifies the resource type being returned. However, given the absence of an output schema, it should ideally describe the return structure (e.g., zone IDs, names, and DNS configurations) and mention pagination behavior.

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?

Input schema has 100% description coverage with clear documentation for 'profile', 'region', and 'max_items' parameters. The description adds no parameter-specific guidance beyond what the schema already provides, meeting the baseline score for high-coverage schemas.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description provides a specific verb ('List') and resource ('Route53 hosted zones') with helpful scoping context ('DNS domains managed by this account'). It implicitly distinguishes from sibling 'aws_route53_get_hosted_zone' (singular retrieval) and 'aws_route53_list_resource_record_sets' (different resource type) through standard naming conventions, though it doesn't explicitly contrast with these alternatives.

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 states what the tool does but provides no guidance on when to use it versus alternatives like 'aws_route53_get_hosted_zone' for specific zone details. There is no mention of pagination behavior with 'max_items' or prerequisites like AWS authentication configuration.

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