Skip to main content
Glama

list_cloudfront_distributions

Retrieve CloudFront distribution details including domain names and status to monitor content delivery network configurations.

Instructions

Lists CloudFront distributions with their domain names and status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function that lists CloudFront distributions using ListDistributionsCommand on the CloudFrontClient and formats the response.
    if (name === "list_cloudfront_distributions") {
        const command = new ListDistributionsCommand({});
        const response = await cloudFrontClient.send(command);
    
        const dists = response.DistributionList?.Items?.map(d => ({
            Id: d.Id,
            DomainName: d.DomainName,
            Status: d.Status,
            Enabled: d.Enabled,
            Aliases: d.Aliases?.Items
        })) || [];
    
        return { content: [{ type: "text", text: JSON.stringify(dists, null, 2) }] };
    }
  • src/index.ts:753-757 (registration)
    Registration of the "list_cloudfront_distributions" tool in the ListToolsRequestSchema handler, including its description and input schema.
        name: "list_cloudfront_distributions",
        description: "Lists CloudFront distributions with their domain names and status.",
        inputSchema: { "type": "object", "properties": {} }
    },
    {
  • Input schema definition for the tool (empty object, no parameters).
    },
  • Import of the CloudFront SDK client and command used by the tool handler.
    import { CloudFrontClient, ListDistributionsCommand } from "@aws-sdk/client-cloudfront";
  • Initialization of the CloudFrontClient instance used in the tool handler.
    const cloudFrontClient = new CloudFrontClient({});
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. It mentions the output includes 'domain names and status' but doesn't cover pagination, rate limits, authentication requirements, error conditions, or whether this is a read-only operation. For a tool with zero annotation coverage, this leaves significant behavioral gaps.

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 communicates the core functionality without unnecessary words. It's appropriately sized and front-loaded with the essential information.

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 simple list tool with no parameters and no output schema, the description provides basic functionality but lacks details about output format, pagination, or behavioral constraints. Given the absence of annotations and output schema, it should provide more context about what to expect from the operation.

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 zero parameters with 100% schema description coverage, so the schema already fully documents the parameter situation. The description appropriately doesn't discuss parameters, which is correct for a parameterless tool, earning a baseline 4.

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 tool's purpose with a specific verb ('Lists') and resource ('CloudFront distributions'), including what information is returned ('domain names and status'). It doesn't explicitly differentiate from sibling tools, but the resource specificity makes its purpose clear.

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, prerequisites, or contextual constraints. It simply states what the tool does without addressing usage scenarios or comparisons with other tools.

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