cloudflare-mcp-pro

create_queue

Create a new Cloudflare Queue. Preview the operation without executing, then confirm with human approval to create the queue.

Instructions

Create a new Cloudflare Queue. Requires confirm:true (human-approval gate); without it returns a preview only.

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": {
      "queue_name": "<queue_name>"
    },
    "name": "create_queue"
  }
}

Input Schema

Name	Required	Description
`account_id`	No	Cloudflare account ID. Falls back to CLOUDFLARE_ACCOUNT_ID env var when omitted.
`queue_name`	Yes	Name for the new queue.
`confirm`	No	Human-approval gate: must be true to actually perform this mutating operation. Omit or set false to get a non-executing preview of what would happen (with secrets redacted). A human should approve before this is set to true.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Jun 22, 2026

TDQS

A4.2/5.0

Behavior4/5

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

The description adds critical behavioral context beyond annotations: it states that the operation is mutating but gated by confirm: true, and that omitting it yields a preview. This compensates for annotations that only indicate non-readonly, non-destructive, non-idempotent.

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?

Two short, front-loaded sentences with zero waste. The first states the purpose, the second explains the essential confirm behavior.

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?

The description covers the core functionality and the conditional preview behavior. However, it does not mention what happens on success (e.g., returns queue details). Given no output schema, a brief note on response would improve completeness, but the current description is still sufficient.

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 baseline is 3. The description reinforces the confirm parameter's role but adds no new semantic meaning beyond what the schema already provides for account_id (fallback) and queue_name (name).

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 'Create a new Cloudflare Queue' which is a specific verb and resource. It distinguishes from sibling create tools by the resource type and adds the confirm/preview behavior.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly says 'Requires confirm:true (human-approval gate); without it returns a preview only.' This gives clear guidance on how to invoke the tool, though it does not compare to alternatives (but alternatives are different resources, so differentiation is inherent).

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

Deploy Server