Skip to main content
Glama

Dateien hochladen lassen

upload_link
Read-only

Gibt die Adresse im Portal, unter der der Kunde Bilder, Videos, PDFs, Schriften oder eine ganze Website als ZIP in den Workspace legt. Bilder gehen nie durch den Chat – diese Adresse dem Kunden nennen, ihn hochladen lassen und danach mit fs_list nachsehen, was angekommen ist. Hast du die Dateien selbst (Dateizugriff, Terminal), enthält die Antwort eine kurzlebige Adresse, unter der du ein ZIP direkt hochlädst. Dateien landen unter assets/uploads, wenn nichts anderes gewählt wird.

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": {
      "website": "<website>"
    },
    "name": "upload_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
dirNoZielordner im Workspace (Standard: assets/uploads; «/» = Webroot, etwa für ein ZIP der ganzen Website).
websiteYesKennung oder Name der Website. Reicht der Zugang ueber mehrere Organisationen und gibt es die Kennung mehrfach, «organisation/website» schreiben.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered; the description goes further by explaining that the delivered URL is short-lived for self-upload, that files land in assets/uploads by default, and that the customer link should be followed by an fs_list check. It stops short of stating whether the customer link expires or what permissions the customer needs.

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?

Four sentences, front-loaded with what the tool returns, then the two usage modes. Every sentence carries information, though the first sentence is long and stacks the accepted file types in a way that slightly delays the core point.

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?

For a two-parameter tool with no output schema, the description does the necessary work by describing what the response contains (a portal address and, for the agent's own uploads, a short-lived direct-upload URL) and where files land. Error handling for an unknown website identifier is not covered, but nothing essential to calling it 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 description coverage is 100%, so both parameters are already documented, including the assets/uploads default, the «/» webroot case, and the organisation/website disambiguation. The description restates the default folder rather than adding new meaning, so 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?

The description states a precise outcome: it returns a portal address where the customer drops images, videos, PDFs, fonts or a full-site ZIP into the workspace. It also covers the second mode (a short-lived direct-upload address when the agent has its own file access), so an agent knows exactly what it produces rather than guessing from the name upload_link.

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?

Explicit routing is given: images never go through chat — name the address to the customer, let them upload, then verify with fs_list. The alternative path is equally explicit: if you already have the files (file access, terminal), use the short-lived address in the response to push a ZIP directly. Both branches are named with their conditions.

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.

Resources