Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Cloudflare: List r2 buckets

cloudflare_list_r2_buckets
Read-only

List R2 buckets in a Cloudflare account by Account ID to retrieve bucket names, creation dates, and storage class details for inventory and auditing.

Instructions

[UNIFIED] List R2 buckets in the account (requires R2 read permission and Account ID). Returns bucket names, creation dates and storage class info.

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": {
      "site": "<site>"
    },
    "name": "cloudflare_list_r2_buckets"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYes
cursorNo
per_pageNo
account_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0

TDQS

B3.4/5.0
Behavior4/5

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

With readOnlyHint=true already covering the safety profile, the description still adds real context: the required permission scope and account-ID dependency, plus the fields returned (names, creation dates, storage class) in the absence of an output schema. It omits pagination behavior despite the cursor/per_page parameters, which keeps it off a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the action and scope followed by the permission prerequisite and return contents. The bracketed '[UNIFIED]' tag is the only wasted token.

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?

It covers authentication prerequisites and return shape, which is the important part for a read-only list tool with no output schema. However, with four parameters at 0% schema coverage, the undefined site and pagination semantics leave an agent guessing at invocation details.

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

Parameters2/5

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

Schema coverage is 0%, so the description carries the full burden, yet only 'account_id' is hinted at ('requires Account ID'). The required 'site' parameter and the pagination parameters (cursor, per_page) get no explanation of format, defaults, or interaction.

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?

States a specific verb+resource ('List R2 buckets') and narrows scope to the account, which separates it from cloudflare_get_r2_bucket and the create/delete siblings. The '[UNIFIED]' prefix adds noise but does not obscure the purpose.

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?

Gives a prerequisite ('requires R2 read permission and Account ID') but never states when to choose this over cloudflare_get_r2_bucket for a single bucket, nor any exclusion. Usage is implied rather than directed.

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