qencode

list_objects

Read-onlyIdempotent

Browse the contents of a Qencode Media Storage bucket.

Args:
    bucket: bucket name (see `list_buckets`). An unknown bucket fails with
        `bucket_not_found`.
    prefix: optional key prefix to filter by (e.g. `raw/`).
    continuation_token: pass the `next_token` from a previous truncated
        response to fetch the next page.

Returns `{objects, is_truncated, region, public}` plus `next_token` when
truncated. Each object has `key`, `size`, `last_modified`, `extension`
(from the key, e.g. `m3u8` / `mp4` / `""`), `destination_url` (that
object's S3 URL — private `source` / stitch / subs / logo, not dest),
and `cdn_url` when the bucket is public (playback and public fetch).
Copy those URLs; do not assemble them. Job dest is always a NEW path
`{destination_prefix}/{new filename or folder}` from `list_buckets`.
Public playback is `cdn_url`. A private progressive file (`.mp4` / `.webm`)
plays via `get_download_url`. Do not call `get_download_url` for HLS/DASH.
One call returns up to ~1000 objects; page with
`continuation_token=next_token` when `is_truncated` is true.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`bucket`	Yes
`prefix`	No
`continuation_token`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`error`	No
`public`	No
`region`	No
`objects`	Yes
`next_token`	No
`is_truncated`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedSep 23, 2026
- addedOutput schema / properties / objects / items / properties / cdn_url
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / objects / items / properties / destination_url
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / objects / items / properties / extension
```
Added value: +{
+  "type": "string"
+}
```
- changedOutput schema / properties / objects / items / required
```
Previous value: -[
-  "key",
-  "size",
-  "last_modified"
-]New value: +[
+  "key",
+  "size",
+  "last_modified",
+  "extension"
+]
```
- addedOutput schema / properties / public
```
Added value: +{
+  "type": "boolean"
+}
```
- addedOutput schema / properties / region
```
Added value: +{
+  "type": "string"
+}
```
Changed1 schema field changedSep 8, 2026
- addedOutput schema / properties / error
```
Added value: +{
+  "type": "string"
+}
```
First observedAug 12, 2026

TDQS

A5/5.0

Behavior5/5

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

Annotations already declare readOnly, idempotent, and non-destructive behavior; the description adds substantial context on top: `bucket_not_found` failures, pagination limits (~1000 objects), truncation semantics, and the distinction between public CDN URLs and private object URLs. This goes well beyond what the annotations provide.

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 long but densely informative: a one-line purpose, an Args section, and a Returns/usage section. Every sentence adds operational value, such as 'Copy those URLs; do not assemble them' and 'page with continuation_token=next_token when is_truncated is true'. The structure makes the information easy to scan.

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?

Given the tool's complexity and the lack of schema-level descriptions, the description is remarkably complete. It covers required input, return shape, pagination, error cases, bucket relationships, URL semantics, and playback behavior. Even with an output schema indicated, this description ensures an agent can call and interpret the tool correctly without further lookup.

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

Parameters5/5

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

Schema description coverage is 0%, so the description carries the full burden for all three parameters. It explains `bucket` with error behavior, `prefix` with a concrete example (`raw/`), and `continuation_token` with its relationship to `next_token` from a truncated response. This gives the agent everything needed to populate the arguments correctly.

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 opens with a specific verb and resource ('Browse the contents of a Qencode Media Storage bucket'), immediately making the tool's scope clear. It also differentiates from siblings by referencing `list_buckets` for bucket names and `get_download_url` for playback, so an agent can distinguish list operations from bucket-level or URL-generation tools.

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?

The description gives practical when-to-use guidance: browse objects, filter by prefix, and page with `continuation_token`. It explicitly warns against calling `get_download_url` for HLS/DASH and explains that private progressive files use it, which routes the agent to the correct sibling tool.

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.