Skip to main content
Glama

request_media_upload

Requests a UI widget to allow the user to directly upload a media file (image, video, audio) from their browser. Use this when the user wants to provide their own media for a plugin. Wait for the user to upload the file, the tool will return the uploaded URL.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "request_media_upload"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only say this is non-read-only, open-world and non-destructive; the description adds the crucial operational facts that a UI widget is surfaced, that the call blocks until the user uploads, and that the returned value is the uploaded URL. It does not cover cancellation, timeout, or failure behavior when the user abandons the widget.

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 short sentences, front-loaded with what the tool does, followed by the trigger condition and the blocking/return contract. No redundant restatement of the name or filler wording.

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 zero-parameter, no-output-schema tool the description covers everything an agent needs: the trigger, the fact that a human must act, that the call waits, and that the result is a URL. Nothing material is missing given the tool's simplicity.

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?

The tool takes no parameters (schema coverage 100%, zero properties), so there is nothing for the description to disambiguate; baseline for a parameterless tool applies. The description correctly avoids inventing inputs.

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 ('Requests a UI widget to allow the user to directly upload a media file') and scopes the media types (image, video, audio). It implicitly contrasts with URL-based import by emphasizing 'directly... from their browser' and 'their own media', though it never names the import_media_from_url sibling explicitly.

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?

'Use this when the user wants to provide their own media for a plugin' gives a clear trigger condition, and it clarifies this is a user-driven operation rather than a programmatic one. It does not state when to prefer the URL-import path instead, leaving that inference to the agent.

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