Skip to main content
Glama

blob_put

Upload a file or inline text to project storage via direct-to-S3. Set visibility to public (CDN) or private, and use immutable mode for permanent, cache-proof URLs.

Instructions

Upload a blob (file or inline content) to project storage via direct-to-S3. Accepts local_path (any size up to 5 TiB) or content (≤ 1 MB inline). Public blobs get a CDN URL; private blobs require authenticated reads. Use immutable: true to produce a content-addressed URL that never needs cache invalidation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesProject ID
keyYesDestination key (path in the project's blob namespace). No leading slash. Example: 'images/logo.png' or 'circuits/v1.zkey'.
local_pathNoPath to a local file to upload. Mutually exclusive with `content`.
contentNoInline content to upload (UTF-8 string). For small blobs ≤ 1 MB. Mutually exclusive with `local_path`.
content_typeNoMIME type (auto-detected from file extension if omitted).
visibilityNoDefault: public. Public blobs get a CDN URL; private blobs require authenticated reads.
immutableNoWhen true, the returned URL includes a content-hash suffix so overwrites produce distinct URLs. CLI auto-computes sha256.
Behavior4/5

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

With no annotations provided, the description takes on full burden. It discloses size limits (5 TiB for local_path, 1 MB for content), CDN URL for public blobs, authenticated reads for private, and immutable content-addressed URLs. However, it does not mention the return value or side effects like overwrites.

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?

Three concise sentences front-load the main action and use bullet-like details for clarity. Every sentence earns its place with no fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema, the description should explain return values (e.g., URL). It covers upload mechanism, constraints, and options, but omits what the tool returns, which is a significant gap for an upload tool.

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 covers all 7 parameters with descriptions, so baseline is 3. The description adds value by explaining size limits, MIME auto-detection, and behavior of visibility and immutable, going beyond the schema.

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 clearly states the tool uploads a blob to project storage via direct-to-S3, specifying it accepts file or inline content. This distinguishes it from siblings like blob_get (retrieval) and blob_rm (deletion).

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?

The description provides clear context for when to use the tool (uploading files or inline content) with size constraints, but does not explicitly mention when not to use it or compare to sibling tools beyond their names.

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/kychee-com/run402'

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