AutoPoster AI

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.

Input Schema

TableJSON Schema

Name	Required	Description
`url`	No	Optional public image or video URL or data URI to upload into media library.
`file`	No	File object provided by ChatGPT for AI-generated images or uploaded files.
`name`	No	Optional display name or title for the media file.

Output Schema

TableJSON Schema

Name	Required	Description
`url`	Yes	Public URL of the media file.
`name`	No	Display name or file name.
`type`	No	Media type ('image' or 'video').
`usage`	No	Guidance on using the media item in posts.
`mediaId`	Yes	ID of the newly uploaded media item.
`message`	No	Upload status message.
`mediaUrl`	No	Public URL of the media file to pass in posts.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 7, 2026

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"
+}

First observedOct 7, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations declare the write/open-world profile, so the description only needs to add operational context, which it does: the 100MB chat download limit and the 5GB direct-S3 path. It omits auth requirements and what happens on failure, but the size boundaries are meaningful behavioral detail.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four sentences, front-loaded with the core purpose, then sources, then the size constraint and fallback. Slight redundancy between the 100MB mention and the >100MB restatement, but nothing is padding.

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?

With an output schema present, return values need no explanation, and the description covers sources, size limits, and the escalation path to the sibling tool. It leaves auth/permission expectations unstated, which is the only real gap.

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 already 100%, so the baseline is 3; the description goes further by mapping scenarios to parameters (ChatGPT file objects vs. public URL/data URI) and by tying the url/file choice to a size threshold, which helps the agent pick the right input.

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 enumerates the accepted source types, so the agent knows exactly what this tool does versus its sibling autoposter_get_media_upload_url.

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 explicit when-to-use conditions (ChatGPT-generated files in /mnt/data/, uploaded files, public URLs), a hard threshold (>100MB), and a named alternative (autoposter_get_media_upload_url for S3 uploads up to 5GB). The routing decision is fully specified.

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

All AutoPoster AI tools Inspect

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

Need Help?