quickS3

Create share link

create_share_link

Create a public share link for one object. Anyone with the link can download the file without a quickS3 account until the link expires. Use this tool only when the user asks to share a file with someone. To download a file yourself, use create_download_link. This tool needs Read and Share on the file. The link stops working if this access grant is revoked or expires. It also stops working if Read or Share on the file is removed, or if the organisation turns share links off.

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
`expiresInSeconds`	No	How long the link stays valid, in seconds: from 300 (5 minutes) to 2592000 (30 days). Default 86400 (24 hours).

Output Schema

Name	Required	Description	Default
`shareUrl`	Yes
`expiresAt`	Yes
`shareLinkId`	Yes
`limitedByGrant`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

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"
+    },
+    "limitedByGrant": {
+      "type": "boolean"
+    },
+    "shareLinkId": {
+      "type": "string"
+    },
+    "shareUrl": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "shareUrl",
+    "shareLinkId",
+    "expiresAt",
+    "limitedByGrant"
+  ],
+  "type": "object"
+}

First observedSep 16, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Goes well beyond the annotations by disclosing that the link grants anonymous public download access, that it requires Read and Share permissions, and the full set of conditions under which the link dies (grant revoked/expired, Read or Share removed, org disables share links). This is the kind of auth and lifecycle context an agent genuinely needs before creating a public link.

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?

Front-loads the action and audience, then the usage condition, then prerequisites, then failure modes. Every sentence carries distinct, non-redundant information with no filler.

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?

Covers purpose, routing to an alternative, permission requirements, and link lifespan/revocation semantics. With annotations, a full input schema, and an output schema present, nothing an agent needs to invoke this correctly is missing.

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 four parameters including the expiresInSeconds range and default. The description only alludes to expiry ("until the link expires") without adding syntax or constraints, so the baseline 3 applies.

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?

States a specific verb and resource ("Create a public share link for one object") and immediately distinguishes the produced artifact from the sibling create_download_link. An agent can tell exactly what this tool does and how it differs from the other link-creating tool.

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?

Explicitly states when to use it ("only when the user asks to share a file with someone") and names the alternative for the other case ("To download a file yourself, use create_download_link"). Both the when and the when-not are covered with a named sibling.

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?