Skip to main content
Glama
webapper-services

CloudSee Drive MCP Server

by webapper-services
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Create share link

share_link

Generate a shareable link for any file in a CloudSee drive. Set expiry in hours (default 12, max 30 days). The link publishes the file publicly until expiry; revocation only via dashboard.

Instructions

Create a shareable link to a file. Requires the drive (bucketName). Optionally set expireTime in hours (default 12 hours, capped at 30 days). Returns a CloudSee share page URL with its expiry and a share id. This is a write: it publishes the file to anyone who holds the link until the share expires, and no tool can list or revoke shares — an unwanted share can only be revoked from the CloudSee dashboard.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filePathYesObject key (path) of the file to share, within the drive.
storageIdNoOptional storage/index id.
bucketNameNoThe CloudSee drive (S3 bucket) name to operate in, e.g. 'max-2778abc0' — find it in the CloudSee dashboard. Required unless CLOUDSEE_DEFAULT_BUCKET is configured on the server.
expireTimeNoHow long the link stays valid, in hours. Defaults to 12 hours when omitted; the server caps it at 30 days.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.1.1
    • addedInput schema / properties / expireTime
      Added value: +{
+  "description": "How long the link stays valid, in hours. Defaults to 12 hours when omitted; the server caps it at 30 days.",
+  "exclusiveMinimum": 0,
+  "type": "number"
+}
  2. First observedv1.0.0

TDQS

A4.5/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 this is a write that publishes the file to anyone with the link until expiry. It also states that no tool can list or revoke shares, and that the only revocation path is the dashboard. This is exactly the kind of behavioral context an agent needs.

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 four sentences with no filler: purpose, requirements, return value, and critical side-effect warning. The warning is placed at the end where it still reads naturally and is easy to retain.

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?

Even without an output schema, the description explains what is returned: a CloudSee share page URL, its expiry, and a share id. Combined with 100% schema coverage and annotations covering mutation and non-idempotence, an agent has everything needed to call the tool correctly and set expectations about irreversibility.

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 baseline is 3. The description restates the expireTime default and cap and the conditional bucketName requirement, both of which are already present in the schema. It adds little new meaning beyond the structured parameter documentation.

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 opens with a specific verb and resource: 'Create a shareable link to a file.' It clearly distinguishes this tool from sibling tools like download_file, move_file, and delete_files because it is the only one about creating public share links.

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

Usage Guidelines4/5

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

The description gives clear operational context: use this tool to create an expiring shareable link, with the bucketName requirement and expiry defaults explained. It also warns that listing or revoking shares is not possible through this or any tool, directing revocation to the CloudSee dashboard. It does not explicitly name alternative tools, but there are no sharing siblings, so the usage context is still clear.

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

Deploy Server

Other Tools