Skip to main content
Glama

AutoPoster AI

by ai.autoposter
OverviewDiscussionsAdmin

Upload Media File

autoposter_upload_media

Uploads an image or video to Auto Poster media library. Accepts files generated in ChatGPT (e.g. DALL-E images in /mnt/data/), uploaded files, or public image URLs. Direct chat download limit is 100MB. For larger videos or files (>100MB), tell the user to provide a direct public file URL or use autoposter_get_media_upload_url for direct S3 upload up to 5GB. If the image exists only in the chat or on the user's device and cannot be sent here, use autoposter_create_upload_link instead.

Input Schema

NameRequiredDescriptionDefault
urlNoOptional public image or video URL or data URI to upload into media library.
fileNoFile object provided by ChatGPT for AI-generated images or uploaded files.
nameNoOptional display name or title for the media file.

Output Schema

NameRequiredDescriptionDefault
urlYesPublic URL of the media file.
nameNoDisplay name or file name.
typeNoMedia type ('image' or 'video').
usageNoGuidance on using the media item in posts.
mediaIdYesID of the newly uploaded media item.
messageNoUpload status message.
mediaUrlNoPublic URL of the media file to pass in posts.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "mediaId": {
+      "description": "ID of the newly uploaded media item.",
+      "type": "string"
+    },
+    "mediaUrl": {
+      "description": "Public URL of the media file to pass in posts.",
+      "type": "string"
+    },
+    "message": {
+      "description": "Upload status message.",
+      "type": "string"
+    },
+    "name": {
+      "description": "Display name or file name.",
+      "type": "string"
+    },
+    "type": {
+      "description": "Media type ('image' or 'video').",
+      "type": "string"
+    },
+    "url": {
+      "description": "Public URL of the media file.",
+      "type": "string"
+    },
+    "usage": {
+      "description": "Guidance on using the media item in posts.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "mediaId",
+    "url"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations declare write (readOnlyHint=false), open-world, and non-destructive, so the safety profile is already covered. The description adds genuinely useful behavioral context beyond that: the 100MB direct-download ceiling, the 5GB S3 path, and the source-type constraints that determine whether the call will succeed. It does not mention auth requirements or failure modes, which keeps it short of a 5.

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 main capability and the size ceiling are front-loaded, then the two escape hatches follow in descending order of relevance. Every sentence carries a routing decision; there is no filler.

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?

An output schema exists, so return values need not be described. Between the accepted sources, the size limits, and the two named alternatives, an agent has everything needed to decide whether to call this tool and how to escalate when it cannot.

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% and both 'url' and 'file' are already documented in the schema, including the data-URI and ChatGPT file-object semantics. The description's source list (DALL-E output, uploads, public URLs) largely restates that, adding only the size context. Baseline 3 is appropriate.

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?

States a specific verb and resource ('Uploads an image or video to Auto Poster media library') and immediately scopes the accepted input sources. It explicitly distinguishes itself from the two most confusable siblings, autoposter_get_media_upload_url and autoposter_create_upload_link, so an agent can route without opening any schema.

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?

Gives concrete when-to-use conditions: use this tool for ChatGPT-generated files, uploaded files, or public URLs up to 100MB; use autoposter_get_media_upload_url for >100MB / S3 uploads up to 5GB; use autoposter_create_upload_link when the asset exists only in chat or on the user's device. Alternatives are named with the exact condition that selects each.

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

All AutoPoster AI 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