qencode

get_download_url

Read-onlyIdempotent

Return a time-limited download URL for an existing object.

Args:
    bucket: bucket name. An unknown bucket returns
        `{url: "", method: "GET", error: "..."}` — not an MCP error.
        Call `list_buckets` and retry with a listed name.
    key: full object key (e.g. `out/result.mp4`). A missing key returns
        the same envelope with recovery instructions; call `list_objects`
        and retry with a listed key. Do not retry the same key.
    expires: presigned-URL lifetime in seconds, clamped to [300, 600].
        Values outside the range are silently clamped, not rejected.

Returns `{url, method: "GET", expires_at}`. The `url` is always a presigned
GET URL that stops working at `expires_at` (a timestamp within the clamped
[300, 600] s window) — this holds for every bucket, regardless of its
`public` flag. It is not a permanent link. A lasting link to watch or share
a public object is `cdn_url` from `list_objects` (`cdn_origin` + `/` + key).
A private progressive file (`.mp4` / `.webm`, no `cdn_url`) is played by
passing this `url` to `open_player`. Do not append anything — an extra
query parameter breaks the signature. Do not pass this `url` to
`open_player` for HLS/DASH, and do not use it as an HLS `source`.

Also use it to download a private object or to feed `fetch_job_result`.
Encode inputs use `cdn_url` (public) or `destination_url` (private), not
this presigned GET.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`key`	Yes
`bucket`	Yes
`expires`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`url`	Yes
`error`	No
`method`	Yes
`expires_at`	No

Schema Changelog

Changes observed during successful MCP inspections.

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 establish readOnly, idempotent, and non-destructive hints, so the bar for extra value is higher. The description goes far beyond that by disclosing the error envelope behavior, silent clamping of expires, the fact that the URL always expires regardless of public flag, signature fragility, and the exactly suitable consumer (open_player for progressive files only). This is rich, non-obvious behavior an agent must know.

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?

Every sentence earns its place. The description opens with a clear one-line purpose, then structures Args, Returns, safe/invalid usage, and exclusions. Despite being long, the length is justified by the subtle failure modes (signature corruption, HLS/DASH misuse, permanent vs. temporary links) that would otherwise cause incorrect calls.

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?

The description covers inputs, output shape, error semantics, time expiration, safe downstream uses, and explicit exclusions. It identifies all relevant sibling relationships (list_buckets, list_objects, open_player, cdn_url, destination_url, fetch_job_result) and explains how the returned URL relates to each. Given the tool's complexity secret, this is complete.

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 must carry the full meaning for bucket, key, and expires. It does: bucket errors are envelope-style, key errors include recovery instructions, and expires is clamped to [300, 600] rather than rejected. It also explains the `url` and `expires_at` output fields, adding meaning the bare schema cannot provide.

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 sentence says exactly what the tool does: 'Return a time-limited download URL for an existing object.' The description also names specific sibling alternatives like list_objects, cdn_url, and open_player, so the tool's role is clearly distinguished from related operations.

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 is exceptionally explicit about when to use this tool: download a private object or feed fetch_job_result, and when not to: encode inputs should use cdn_url/destination_url, and this URL must not be used for HLS/DASH. It also instructs the agent to call list_buckets or list_objects and retry with a valid name rather than retrying the same key, giving actionable routing guidance.

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.