Skip to main content
Glama
Sign In
cloudflare-mcp-pro

cloudflare-mcp-pro

by helbertparanhos
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_email_destinations

Read-only

List all verified Email Routing destination addresses in a Cloudflare account. Provides an overview of configured email destinations for routing.

Instructions

List verified Email Routing destination addresses in an 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": "list_email_destinations"
  }
}

Input Schema

NameRequiredDescriptionDefault
account_idNoCloudflare account ID. Falls back to CLOUDFLARE_ACCOUNT_ID env var when omitted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is clear. The description adds behavioral context by specifying that only 'verified' destinations are listed, which is beyond what annotations provide. 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 sentence with no wasted words. It directly conveys the tool's action, resource, 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 tool's simplicity (one optional param, no output schema, readOnly annotations), the description sufficiently conveys what the tool does and returns. It could optionally mention the response is a list or that it requires routing permission, but the current state is adequate.

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?

Schema coverage is 100%, so the schema fully documents the account_id parameter including its fallback behavior. The description does not add any parameter-specific information beyond the scope 'in an account', which is already implied. Baseline of 3 is appropriate.

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 the tool lists verified Email Routing destination addresses in an account. The verb 'list' and specific resource 'verified Email Routing destination addresses' make its purpose unambiguous and distinguish it from related tools like list_email_rules.

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 the tool is for listing destinations, but it does not explicitly state when to use it compared to alternatives (e.g., list_email_rules) or when not to use it. No exclusions or context are 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