Skip to main content
Glama

request_upload_url

Generate a presigned upload URL for large artifacts (500 MB to 5 GB) to upload directly to R2 storage, avoiding size limits of store_artifact.

Instructions

Reserve a presigned R2 PUT URL for a file too large to send through store_artifact (over 500 MB up to 5 GB). Returns an upload_url, headers to include in the PUT, and an artifact_id in pending state. The agent (or its environment) PUTs the bytes directly to R2, then calls complete_upload. Pro plan only. Most agents should use store_artifact and let the MCP server pick the path automatically.

Not retry-safe: this endpoint does not support idempotency keys, so on an HTTP 5xx or network error the reservation may or may not have been created. Do NOT blindly retry — the error guidance tells you to first call list_artifacts with the same session_id/agent_id to detect any pending artifact, so you don't create a duplicate.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filenameYes
content_typeYes
size_bytesYes
session_idNo
agent_idNo
metadataNo
ttlNo
Behavior4/5

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

Annotations only provide readOnlyHint=false. Description adds important context about idempotency and retry handling, but could detail more edge cases.

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 focused paragraphs: purpose/alternative and retry warning. No unnecessary words.

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?

Explains return values and retry safety, but missing explicit parameter explanations for metadata and ttl given no output schema.

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?

With 0% schema coverage, description implies usage of parameters but does not explain each parameter individually (e.g., metadata, ttl). Provides enough for basic understanding but not full detail.

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?

Specifically describes reserving a presigned R2 PUT URL for files too large for store_artifact (over 500 MB up to 5 GB). Distinguishes from sibling tool clearly.

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?

Explicitly states when to use (large files), when not to (most should use store_artifact), and warns about retry safety with alternative detection approach.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/SagaPeak/artifacta-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server