Skip to main content
Glama

create_file_request

Create a link that lets anyone upload files to a folder without signing in, while keeping contents private. Add optional password, deadline, uploader name, subfolders, and upload limits.

Instructions

Create a file request link for a folder: anyone with the link can upload files into it without signing in, but cannot see its contents. Optional password, deadline, uploader name, per-uploader subfolders and size/count limits. Uploads count against this account's quota. Requires shares:write; supports idempotency.

Input Schema

NameRequiredDescriptionDefault
noteNoinstructions shown to uploaders
pathNofolder path, alternative to folder_id
titleYesshown to uploaders, up to 100 characters
passwordNo
folder_idNo
max_filesNo
expires_atNodeadline; uploads started before it may finish
require_nameNouploaders must enter a name
max_file_sizeNobytes per file
idempotency_keyNo
max_total_bytesNobytes in total across all uploads
group_by_uploaderNoput each uploader's files in a subfolder named after them (implies require_name)

Output Schema

NameRequiredDescriptionDefault
idYes
urlYes
noteNo
titleYes
folder_idYes
max_filesNo
new_countYes
expires_atNo
file_countYes
folder_nameNo
total_bytesYes
has_passwordYes
require_nameYes
max_file_sizeNo
max_total_bytesNo
group_by_uploaderYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

Annotations supply only destructiveHint=false, so the description carries the real burden and does: anonymous uploaders cannot see folder contents, uploads consume this account's quota, shares:write scope is required, idempotency is supported, and the deadline is soft ("uploads started before it may finish"). Those are exactly the non-obvious behaviors an agent needs before calling.

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 dense sentences with the core capability and access model front-loaded, followed by optional features, then operational constraints (quota, auth, idempotency). No sentence restates the name or wastes words.

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 12-parameter mutation tool, the definition covers access model, quota impact, auth scope, idempotency, and expiry semantics; an output schema exists so return values need no explanation. Nothing essential for correct invocation is missing.

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

Parameters4/5

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

Schema coverage is 67%, and the description adds meaning on top: it groups password, deadline, uploader name, per-uploader subfolders, and size/count limits as optional constraints, and states the quota implication of the limit parameters. Undocumented fields like idempotency_key and folder_id versus path are only lightly covered, keeping it below 5.

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?

Opens with a specific verb and resource: "Create a file request link for a folder," and immediately defines the resulting artifact's semantics (anonymous upload-only, contents invisible). That distinguishes it from create_link, create_share, and list_file_requests without the agent needing to open a schema.

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?

The description conveys the scenario clearly (collect files from people without accounts) but never names a sibling alternative or an explicit when-not condition, e.g. versus create_link or create_share. Usage is implied by the capability description rather than stated as routing guidance.

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