Skip to main content
Glama

list_hosted_zones

Retrieve all Route53 hosted zones to manage DNS configurations and domain records in AWS.

Instructions

Lists all Route53 Hosted Zones.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/index.ts:708-714 (registration)
    Registration of the 'list_hosted_zones' tool in the ListToolsRequestSchema handler, including name, description, and empty input schema.
        name: "list_hosted_zones",
        description: "Lists all Route53 Hosted Zones.",
        inputSchema: {
            type: "object",
            properties: {}
        }
    },
  • Handler implementation for 'list_hosted_zones' tool. Sends ListHostedZonesCommand to Route53 client and formats the response with hosted zone details.
    if (name === "list_hosted_zones") {
        const command = new ListHostedZonesCommand({});
        const response = await route53Client.send(command);
    
        const zones = response.HostedZones?.map(z => ({
            Id: z.Id,
            Name: z.Name,
            Config: z.Config,
            ResourceRecordSetCount: z.ResourceRecordSetCount
        })) || [];
    
        return { content: [{ type: "text", text: JSON.stringify(zones, null, 2) }] };
    }
  • Input schema for the tool: empty object (no parameters).
    inputSchema: {
        type: "object",
        properties: {}
    }
  • Initialization of the Route53Client used by the handler.
    const route53Client = new Route53Client({});
  • Import of Route53Client and ListHostedZonesCommand.
    import { Route53Client, ListHostedZonesCommand, ListResourceRecordSetsCommand } from "@aws-sdk/client-route-53";
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 of behavioral disclosure. It states the action ('Lists') but doesn't describe return format, pagination, rate limits, permissions required, or any side effects. This leaves significant gaps in understanding how the tool behaves in practice.

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, efficient sentence that directly states the tool's function without any fluff. It's front-loaded with the core action and resource, making it easy to parse and understand immediately.

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?

Given no annotations and no output schema, the description is incomplete for a tool that likely returns structured data. It doesn't explain what 'Lists' entails (e.g., format, scope, limitations), leaving the agent without crucial context for proper use.

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

Parameters4/5

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

The tool has 0 parameters with 100% schema description coverage, so no parameter documentation is needed. The description appropriately doesn't discuss parameters, focusing instead on the tool's purpose, which aligns with the baseline expectation for parameterless tools.

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 clearly states the verb ('Lists') and resource ('all Route53 Hosted Zones'), making the tool's purpose immediately understandable. It distinguishes itself from siblings like 'list_record_sets' by specifying the resource type, though it doesn't explicitly contrast with other list tools beyond that.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, context, or exclusions, leaving the agent to infer usage based on the resource name alone without explicit direction.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/bhaveshopss/MCP-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server