quickS3

Create share link

create_share_link

Create a public share link for one object. Anyone who has the link can download the file without a quickS3 account, until it expires. Use this only when the user asks to share a file with someone; to download a file yourself, use create_download_link. Needs Read and Share on the file. The link never outlives this access grant: revoking the grant, losing Read or Share on the file, or the organisation switching share links off disables it.

Input Schema

TableJSON 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

TableJSON 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?

The description goes well beyond the annotations by disclosing that the link is public, works without an account, expires, and can be disabled if the access grant is revoked, permissions are lost, or the organization disables share links. This is valuable behavioral context about an externally visible, non-idempotent side effect.

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?

Four sentences deliver purpose, usage guidance, alternative routing, permission requirements, and edge-case behavior with no filler. The most important differentiating facts are front-loaded before the alternative tool is mentioned.

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?

For a tool with this complexity, the description covers what the tool does, when to use it, when not to use it, required permissions, and link lifecycle behavior. The existence of an output schema means return-value documentation is not required in the description, so nothing essential 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 coverage is 100%, so the schema fully documents all four parameters including the valid range and default for expiresInSeconds. The description does not add parameter-level meaning, which is acceptable here because the schema already carries that burden.

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 states a concrete verb and resource: 'Create a public share link for one object.' It also immediately distinguishes itself from create_download_link, making the tool's purpose unmistakable among siblings.

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?

It explicitly says 'Use this only when the user asks to share a file with someone' and names the alternative 'to download a file yourself, use create_download_link.' It even states required permissions, leaving no ambiguity about when this tool should be selected.

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?