Skip to main content
Glama
Sign In
Aktar

Aktar

Official
by getaktar
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Create a temporary link

create_temporary_link
Read-only

Generate a presigned download link for a file in a private bucket that expires after a set time, enabling limited-time sharing without changing bucket contents.

Instructions

Make a link to a file in a bucket that stops working after a while (a presigned URL), for private buckets or sharing for a limited time. Anyone with the link can download the file until it expires, even from a private bucket, so only make one when the user asks. Nothing in the bucket changes.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "key": "<key>"
    },
    "name": "create_temporary_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesThe file's key in the bucket (objectKey in search_uploads, key in list_bucket).
minutesNoHow long the link works, in minutes (default 60, at most 60).
destinationNoDestination name or ID. Leave out for the selected one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

A3.9/5.0
Behavior4/5

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

Adds genuine behavioral context beyond the annotations: the link is a presigned URL that expires, anyone holding it can download even from a private bucket, and no bucket state is mutated. The last point is consistent with readOnlyHint=true. Minor gaps remain: whether links can be revoked early and what exactly is returned.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One dense sentence front-loads the action, then the expiry behavior, then the exposure caution. Every clause carries information and nothing is padding, though the run-on structure makes the caution harder to spot than a separate sentence would.

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?

With only three fully documented parameters and no output schema, the definition covers purpose, expiry, and security implications adequately. The remaining shortfall is that the description never says the tool returns the URL itself, which the agent must surface to the user.

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 key, minutes (default 60, max 60) and destination are already fully documented in the schema. The description only echoes the expiry notion with 'stops working after a while' and adds no new meaning, such as whether minutes defaults differently or how destination interacts with the selected destination. 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 ('Make a link to a file in a bucket') and qualifies it precisely as a presigned URL with expiry, which is concrete enough to distinguish it from a generic link tool. It does not explicitly name the sibling create_short_link or explain the difference, so the agent must infer why one link tool is preferred over the other.

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?

Gives a clear positive condition ('for private buckets or sharing for a limited time') and an explicit guardrail ('only make one when the user asks'), which is stronger than most descriptions. It stops short of naming alternatives, so the agent is not told to prefer create_short_link when expiry or public exposure is not required.

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