Skip to main content
Glama

list_buckets

Read-onlyIdempotent

List the Qencode Media Storage buckets available to the account.

Returns a `buckets` array; each entry has `name`, `region`
(us-west / eu-central), `created_at`, and `public`: true when the bucket is
served over an unauthenticated CDN endpoint (readable without a signed URL).
`public` is read-only here — bucket visibility is managed in the Qencode
portal, not via these tools.

Each bucket also carries `destination_prefix` (job `destination.url` =
`{destination_prefix}/{new filename or folder}`) and, when `public` is
true, `cdn_origin`. Copy these strings; do not assemble the host.
Do not copy a listed file's `destination_url` as dest — that is the
existing object (use it as `source`). `s3://<name>/…` is rejected (it is
generic S3, not Media Storage).

Caveat: for a *just-created* bucket the `public` flag is not yet stable — it
starts `false` and flips to `true` within a few seconds up to ~a minute as
the CDN endpoint provisions. Don't cache a `public` value read right after
`create_bucket`; poll until it settles (see qencode://docs/storage).

SCOPE — every storage tool here reuses the caller's existing Qencode
sign-in. There is no separate storage permission and no second approval
prompt, including for the tools that write. They also operate on the WHOLE
ACCOUNT rather than the current project: this call lists every bucket the
account owns, and anything created or written is visible to all of that
account's projects. Surface that to the user before acting on storage on
their behalf.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_buckets"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
errorNo
bucketsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / buckets / items / properties / cdn_origin
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / buckets / items / properties / destination_prefix
      Added value: +{
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • addedOutput schema / properties / error
      Added value: +{
      +  "type": "string"
      +}
  3. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare readOnlyHint/idempotent/non-destructive, and the description goes well beyond them: it discloses account-wide rather than per-project scope, that storage tools reuse the existing sign-in with no separate permission or approval prompt even for writers, and that `public` is an eventually-consistent field after creation. It also tells the agent to surface the account-wide visibility to the user before acting — behavior no annotation conveys.

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-loaded with the purpose, then organized into distinct blocks: return fields, prefix/CDN handling, source-vs-dest warning, consistency caveat, and scope. Every paragraph carries information, though the SCOPE block is generic boilerplate reused across storage tools and the output-field walkthrough is lengthy for a zero-argument list call.

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?

For a zero-param read tool with an output schema and full annotations, this is more than complete: it covers account-wide blast radius, permission/approval behavior, field semantics including eventual consistency, and a pointer to qencode://docs/storage. Nothing an agent needs in order to call it correctly, or to advise a user, 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?

Zero parameters, so there is nothing for the schema to describe and no parameter meaning to add; the baseline applies. The description instead invests its detail in output-field semantics (`region`, `public`, `destination_prefix`, `cdn_origin`), which is useful but belongs to a different dimension.

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?

Opens with a specific verb+resource+scope: "List the Qencode Media Storage buckets available to the account." It implicitly separates the read path from create_bucket (noting `public` is read-only here and managed in the portal) and from list_objects (warning not to copy a listed file's `destination_url`). It does not explicitly name a sibling, which keeps it just short of a 5.

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?

Gives real when/when-not guidance: copy `destination_prefix` rather than assembling the host, don't reuse a file's `destination_url` as dest (it is the source), and `s3://<name>/…` is rejected. The create_bucket caveat (don't cache `public` immediately; poll until stable) is a concrete usage rule. What's missing is explicit routing language like "call this first to obtain a destination before download_url_to_bucket."

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.