quickS3

Create download link

create_download_link

Read-onlyIdempotent

Create a short-lived download link (valid 5 minutes, up to 5 uses) for one object. You can then download the file by following the link, which redirects to a fresh download URL at your storage provider.

Input Schema

Name	Required	Description
`key`	Yes	Object key, e.g. "reports/2026/q3.csv"
`bucket`	Yes	Bucket name
`connectionId`	Yes	Connection ID from list_connections

Output Schema

Name	Required	Description	Default
`url`	Yes
`expiresAt`	Yes
`transferId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 17, 2026

addedOutput schema / properties / url
```
Added value: +{
+  "type": "string"
+}
```

changedOutput schema / required

Previous value: -[
-  "transferId",
-  "expiresAt"
-]New value: +[
+  "url",
+  "transferId",
+  "expiresAt"
+]

Changed1 schema field changedSep 16, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "expiresAt": {
+      "type": "string"
+    },
+    "transferId": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "transferId",
+    "expiresAt"
+  ],
+  "type": "object"
+}

First observedSep 16, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds genuinely useful behavior the annotations cannot convey: the 5-minute TTL, the 5-use cap, and that following the link redirects to a fresh provider URL.

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?

Two sentences, zero waste, with the core action and the headline constraint (short-lived link) front-loaded before the mechanics of following the link.

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

Completeness4/5

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

An output schema exists, so return values need not be explained, and the description covers the essential non-obvious behavior for an external-facing link. The only real gap is a lack of differentiation from the sibling link-creation tools.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents all three required parameters, including the example key format and the list_connections pointer for connectionId. The description adds no parameter-level meaning beyond that, so baseline 3 applies.

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?

States a specific verb and resource ('Create a short-lived download link ... for one object') plus the key constraint (valid 5 minutes, up to 5 uses). It is clear on its own, but it never contrasts with the near-identical sibling create_share_link, so an agent must infer which link type to pick.

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

Usage Guidelines3/5

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

Usage is only implied: it tells you the result is a link you follow to download, but gives no explicit when-to-use or when-not, and no routing against create_share_link or create_upload_url. The context is inferable but not stated.

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

All quickS3 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.

Resources

Need Help?