Skip to main content
Glama

Upload a file from a public URL

upload_file

Import a user-specified public HTTPS file into an accessible project or task. The Edworking backend validates URLs and enforces a 50 MiB/30-second download limit. Do not include credentials in the URL. Other project members may see the file. Preserve requestId on retries.

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": {
      "requestId": "<requestId>",
      "url": "<url>"
    },
    "name": "upload_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPublic HTTPS URL of the file to import. Must not contain credentials or target a private network.
nameNoThe name requested by the user. For updates, omit to keep the current name.
taskIdNoExisting accessible task ID returned by list_tasks or search.
folderIdNoOptional existing destination folder ID. Must be accessible within the target project or task.
projectIdNoExisting accessible project ID returned by list_projects.
requestIdYesA unique UUID for this intended action. Reuse it unchanged when retrying the same action.

Output Schema

NameRequiredDescriptionDefault
fileYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare openWorldHint=true, idempotentHint=false and destructiveHint=false, and the description adds real value beyond them: backend URL validation, download size/time limits, credential prohibition, and file visibility to other project members. It stops short of describing failure modes or what happens on partial download, but the disclosure is well above the annotation baseline.

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 short sentences, front-loaded with the action and destination, then constraints, then the retry rule. No filler or redundancy.

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?

An output schema exists so return values need not be explained; the description covers the remaining gaps an agent needs — size/time limits, credential policy, visibility side effect, and idempotency handling via requestId.

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 all six parameters are already documented, including the requestId retry contract and the URL credential restriction. The description restates those points rather than adding new meaning, 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 (Import) and resource (a user-specified public HTTPS file) plus the destination scope (project or task). An agent can distinguish this from list_files or create_doc without opening the 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?

Gives concrete operating constraints (no credentials in URL, 50 MiB/30-second limit, preserve requestId on retries) but never states when to choose this over alternatives or when not to use it. Usage context is implied rather than explicit.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.