qencode

download_url_to_bucket

Server-side copy of a public URL into a bucket (no transcoding).

The server fetches `source_url` itself and streams the bytes straight into
the bucket via a short-lived presigned upload — use this to ingest an
existing asset into Qencode Media Storage as-is. To store a *transcoded*
result instead, set a `destination` on a transcoding job.

IMPORTANT — this call is synchronous and blocking: it returns only after the
whole file has been fetched and uploaded, and there is no job token or
progress to poll (unlike transcoding). The transfer must finish inside the
presigned upload window (~10 minutes) and is size-capped server-side, so it
suits small/medium assets; very large or slow sources may time out — upload
those out-of-band instead.

Args:
    source_url: a publicly reachable `http(s)` URL the server can fetch
        directly. Non-http(s) schemes and private/loopback hosts are
        rejected up front; a source that responds with a redirect or a
        4xx/5xx fails the transfer. HTTP redirects are not followed (SSRF);
        the tool returns `status: "redirect_not_followed"` with the
        `Location` header when it is a public URL you can pass back in.
    bucket: destination bucket name. Must already exist on this account
        (see `list_buckets`). An unknown name returns
        `status: "bucket_not_found"` with recovery instructions — not an
        MCP error. Call `list_buckets` and retry with a listed name; do
        not retry the same name.
    key: destination object key (e.g. `raw/input.mov`). An existing object
        at this key is refused (`status: "object_exists"`) — this tool
        does not overwrite. Pick a new key.

Returns `{bucket, key, size_bytes, status: "uploaded"}` on success.
Unknown bucket: `{status: "bucket_not_found", error: "..."}` (same
envelope, `size_bytes` 0). Occupied key: `status: "object_exists"`.
Account suspended: `status: "unavailable"`.

SCOPE — this writes using the caller's existing Qencode sign-in: no
separate storage permission, no second approval prompt. The target bucket
belongs to the WHOLE ACCOUNT and is visible to all of its projects. If that
bucket is public, whatever you ingest becomes readable by anyone with its
URL. Act on an explicit request or clear prior context; never ingest
unprompted.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`key`	Yes
`bucket`	Yes
`source_url`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`key`	Yes
`error`	No
`bucket`	Yes
`status`	Yes
`location`	No
`size_bytes`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 8, 2026
- addedOutput schema / properties / error
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / location
```
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?

Beyond the annotations (readOnlyHint=false, idempotentHint=false), the description thoroughly discloses blocking behavior, no progress token, the ~10-minute presigned window, server-side size cap, non-overwrite policy, SSRF rejections, redirect-not-followed behavior, and account-scope/security implications. It also exposes error statuses like 'bucket_not_found' and 'object_exists' so the agent can react correctly.

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 every sentence adds value. It is structured with a concise opening, an IMPORTANT callout, per-parameter explanations, a return-envelope section, and a SCOPE security section. The most critical constraint (synchronous, blocking) is front-loaded, and no filler or repetition exists.

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, the lack of schema descriptions, and the presence of an output schema, the description covers all necessary context: input constraints, error statuses, recovery instructions, side effects, security implications, and success return shape. An agent possesses everything needed to invoke it correctly and safely.

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%, yet the description fully compensates. Each parameter gets precise semantics: source_url must be a public http(s) URL with private/loopback rejection and redirect handling; bucket must already exist and can be verified via list_buckets; key must be a new object key because existing keys are refused. This adds critical meaning beyond the bare schema.

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 opening line states a specific verb and resource: 'Server-side copy of a public URL into a bucket (no transcoding).' It then explicitly contrasts with transcoding jobs ('To store a transcoded result instead, set a destination on a transcoding job'), which distinguishes it from the transcode_video sibling.

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 explicit when-to-use guidance ('use this to ingest an existing asset into Qencode Media Storage as-is') and when-not-to ('very large or slow sources may time out — upload those out-of-band instead'). It also directs to alternative tooling via 'set a destination on a transcoding job.'

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.