Skip to main content
Glama
Sign In

Blaze

by ai.blaze.app
OverviewDiscussionsAdmin

Get media upload URLs

get_media_upload_urls

Get upload URLs for media files that are on the user's computer, so they can be used with schedule_posts. Input: workspace_key and filenames (each with its real extension).

For each filename it returns an upload_url and a hosted_url. Upload each file with an HTTP PUT of its raw bytes to its upload_url, for example curl -X PUT --upload-file <local file> "<upload_url>". Do not add x-amz-acl or any other x-amz-* header; the URL is already signed and S3 rejects extra signed headers. Then pass each hosted_url to schedule_posts as a media url, in carousel order.

The extension sets the media type. Supported images: png, jpeg, webp, svg. Supported videos: mp4, mpeg, webm, quicktime (.mov).

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": {
      "workspace_key": "<workspace_key>",
      "filenames": "<filenames>"
    },
    "name": "get_media_upload_urls"
  }
}

Input Schema

NameRequiredDescriptionDefault
filenamesYesLocal file names to upload, each with its real extension.
workspace_keyYesKey of the workspace to act in. Call list_workspaces to see the workspaces you have access to and their keys.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

The description adds substantial behavioral detail beyond the annotations: it explains that each file gets an upload_url and hosted_url, that the upload must be a raw-byte HTTP PUT, that adding x-amz-* headers will cause S3 to reject the request, and that the filename extension determines the media type. This is exactly the kind of non-obvious context an agent needs to invoke the tool correctly.

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?

The description is front-loaded with purpose and inputs, then moves through a clear sequence: return values, upload procedure, header warning, and final handoff to schedule_posts. Every sentence contributes to correct usage, and the length is justified by the multi-step workflow being described.

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?

There is no output schema, but the description explains the return values (upload_url and hosted_url), the upload mechanics, the supported file types, and the downstream integration with schedule_posts. This is complete enough for an agent to use the tool correctly without additional context.

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 coverage is 100%, so the baseline is 3. The description goes further by emphasizing that filenames must include their real extension and by listing supported extensions and their media types, which adds practical meaning to the filenames parameter 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 states a specific verb and resource: 'Get upload URLs for media files that are on the user's computer.' It explicitly connects the output to schedule_posts and clarifies the scope (local files, not existing media or generated images), which distinguishes it from siblings like search_media and generate_image.

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?

It clearly establishes the use case: local files that need to be uploaded for use with schedule_posts. The workflow is spelled out step by step, including how to upload and what to do with the resulting hosted_url. It does not explicitly name alternatives (e.g., search_media for existing assets), but the context makes the boundary clear.

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

All Blaze toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources