Skip to main content
Glama
backblaze-labs

Backblaze B2 MCP Server

Official

b2_create_bucket

Create a B2 cloud storage bucket, setting access type, CORS rules, lifecycle policies, encryption, and Object Lock.

Instructions

Create a new B2 bucket. Bucket names must be globally unique, 6-63 characters, and contain letters, digits, hyphens, and periods (names are not case-sensitive and cannot start with 'b2-').

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
corsRulesNoCORS rules: <=100. allowedOrigins/allowedOperations require 1-100 non-empty strings; allowedHeaders/exposeHeaders allow <=100. Strings <=999 chars. Per-rule UTF-8 total <1,000. Names unique.
bucketInfoNoCustom metadata: <=10 pairs. Keys: 1-50 UTF-8 bytes, chars A-Z a-z 0-9 . _ ` ~ ! # $ % ^ & * ' | + -, no b2- prefix. Values total <=10,000 UTF-8 bytes.
bucketNameYesThe name for the new bucket. Must be globally unique.
bucketTypeYesallPublic allows unauthenticated downloads; allPrivate requires authorization.
lifecycleRulesNoLifecycle rules for automatic file management.
fileLockEnabledNoEnable Object Lock (file lock) on the bucket at creation. (Object Lock can also be enabled later on an existing bucket via b2_update_bucket.) Must be true before any retention or legal hold can be applied to files in this bucket.
defaultServerSideEncryptionNoDefault server-side encryption for new files in this bucket.
Install Server

TDQS

A3.5/5.0
Behavior2/5

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

The description adds no behavioral context beyond what the annotations already convey: it creates a resource, is not read-only, and is not idempotent. It does not mention authorization requirements, side effects on failure, or what happens if the bucket name already exists.

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 two concise sentences with the primary action front-loaded. The remaining sentence earns its place by capturing important bucket-name constraints that an agent must know before calling.

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?

Given a complex 7-parameter schema with nested objects and no output schema, the description is narrow. It fully covers bucket naming constraints, but omits usage context, required authorization, expected return value, and relationship to sibling bucket operations.

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?

Schema description coverage is 100%, so the baseline is 3. The description adds meaningful parameter nuance beyond the schema for bucketName by specifying global uniqueness, 6-63 characters, allowed characters, case-insensitivity, and the prohibition on a 'b2-' prefix.

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 states a specific action and resource: 'Create a new B2 bucket.' This clearly separates it from siblings like b2_delete_bucket and b2_update_bucket, and the modifier 'new' removes ambiguity about the operation's intent.

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?

There is no guidance about when to use this tool versus alternatives, no prerequisites, and no mention of related tools such as b2_authorize_account or b2_update_bucket. The intended use is only implied by the verb 'Create.'

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

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/backblaze-labs/b2-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server