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

cloudflare-mcp-pro

by helbertparanhos
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_zone_analytics

Read-only

Get HTTP traffic analytics for a zone over a time range via GraphQL.

Instructions

Get HTTP traffic analytics for a zone over a time range (via GraphQL).

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": {
      "zone_id": "<zone_id>",
      "since": "<since>",
      "until": "<until>"
    },
    "name": "get_zone_analytics"
  }
}

Input Schema

NameRequiredDescriptionDefault
zone_idYesThe Cloudflare zone ID (32-char hex). Get it from list_zones.
sinceYesHour-aligned ISO 8601 UTC start, e.g. 2024-01-01T00:00:00Z. httpRequests1hGroups buckets are hourly.
untilYesHour-aligned ISO 8601 UTC end, e.g. 2024-01-02T00:00:00Z.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the description's mention of 'via GraphQL' adds only a minor implementation detail. No additional behavioral traits like required permissions, rate limits, or response structure are disclosed.

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 fluff. Every word adds value, making it highly concise.

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?

While parameters are well-documented, there is no output schema and the description does not explain what the returned analytics data contains (e.g., metrics, structure). This leaves the agent without sufficient context to interpret the response.

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 description coverage is 100% with each parameter described in detail. The tool description does not add extra parameter meaning beyond reaffirming the time range context, so baseline 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 verb 'get', the resource 'HTTP traffic analytics for a zone', and scope 'over a time range'. It distinguishes itself from all sibling tools which are primarily CRUD operations for other resources.

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 does not provide any guidance on when to use this tool versus alternatives, nor does it mention any prerequisites or exclusions. The intended usage is only implied by the tool's unique capabilities among siblings.

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