qencode

create_bucket

Idempotent

Create a bucket in the signed-in Qencode account.

Writes only inside that account. The only inputs are a bucket name and a
region: no URL, no hostname, and no other storage provider. `region` must
be `us-west` or `eu-central`. A name owned by another account returns
`status: "bucket_conflict"` with an `error` string and creates nothing —
not an MCP error. Choose a different name; do not retry this one. A name
this account already has returns `status: "exists"` and does not replace
the bucket.

Call this ONLY on an explicit request to create a bucket or to keep a
result long-term. Do NOT call it just because a transcoding request lacks a
`destination`, or because the user says they have no bucket / nowhere to
save the output — that is the default temp-storage case: omit `destination`
(24-hour temp storage) and disclose it, do not provision an account-level
bucket the user did not ask for.

The bucket belongs to the whole Qencode account and is visible to every
project on that account, not just the current one. The call uses the
caller's existing Qencode sign-in. There is no separate storage permission.

Args:
    name: 6–63 chars, lowercase letters / digits / hyphens
        (`^[a-z0-9][a-z0-9-]{4,61}[a-z0-9]$`) — no underscores or uppercase.
        A name that breaks this pattern is rejected (`invalid_bucket_name`).
    region: `us-west` or `eu-central` only.

Returns `{bucket, region, status, destination_prefix}` plus `cdn_origin`
only after this account's CDN name is ready (a fresh bucket usually omits
it until then):
  - `status: "created"` — a new bucket was provisioned in this account.
  - `status: "exists"` — this account already has that name (no-op).
  - `status: "bucket_conflict"` — another account owns the name. `error`
    explains it. Not an MCP error.
Copy `destination_prefix` into job `destination.url` as
`{destination_prefix}/{new filename or folder}`. Do not assemble the
host and do not copy a listed file's `destination_url` as dest.

Input Schema

Name	Required	Description	Default
`name`	Yes	Bucket name: lowercase letters, digits, and hyphens only.
`region`	Yes	Storage region for the bucket.

Output Schema

Name	Required	Description	Default
`error`	No
`bucket`	Yes
`region`	Yes
`status`	Yes
`cdn_origin`	No
`destination_prefix`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 2, 2026
- addedInput schema / properties / name / description
```
Added value: +"Bucket name: lowercase letters, digits, and hyphens only."
```
- addedInput schema / properties / name / maxLength
```
Added value: +63
```
- addedInput schema / properties / name / minLength
```
Added value: +6
```
- addedInput schema / properties / name / pattern
```
Added value: +"^[a-z0-9][a-z0-9-]{4,61}[a-z0-9]$"
```
- addedInput schema / properties / region / description
```
Added value: +"Storage region for the bucket."
```
- addedInput schema / properties / region / enum
```
Added value: +[
+  "us-west",
+  "eu-central"
+]
```
Changed2 schema fields changedSep 23, 2026
- addedOutput schema / properties / cdn_origin
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / destination_prefix
```
Added value: +{
+  "type": "string"
+}
```
Changed1 schema field changedSep 8, 2026
- addedOutput schema / properties / error
```
Added value: +{
+  "type": "string"
+}
```
First observedAug 12, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=true, openWorldHint=false), but the description adds substantive context: conflict handling returns `status: bucket_conflict` rather than an MCP error, an existing name is a no-op that does not replace the bucket, the bucket is account-wide and visible to every project, and no separate storage permission is needed. It even states `cdn_origin` is often absent on a fresh bucket.

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?

Front-loads the core operation and the critical do-not-provision warning; the Args and Returns blocks are dense and structured. It is long, but nearly every sentence carries decision-relevant content, with only mild repetition between the prose and the Args section.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, yet the description still usefully maps the status values and explains how to consume `destination_prefix` in a job's `destination.url`. Combined with the scoping, permissions, and conflict guidance, nothing an agent needs to call this correctly is missing.

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 coverage is 100%, so the baseline is 3, but the description adds real meaning beyond the schema: the reject code (`invalid_bucket_name`) for a pattern violation and the consequence of each `region` value. It largely mirrors the schema's regex and enum, which caps it below 5.

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?

States a specific verb and resource — 'Create a bucket in the signed-in Qencode account' — and immediately scopes it against siblings like list_buckets and download_url_to_bucket by declaring it writes only inside that account with no other storage provider. An agent can identify the operation without opening the schema.

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

Usage Guidelines5/5

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

Explicit when-to-use ('ONLY on an explicit request to create a bucket or to keep a result long-term') and an equally explicit when-not-to-use, naming the tempting-but-wrong case (missing `destination` on a transcode) and the correct alternative behavior (omit `destination`, use 24-hour temp storage). It also tells the agent not to retry on a conflict.

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

All qencode tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.