Skip to main content
Glama

Upload Media File

autoposter_upload_media

Uploads an image or video to Auto Poster media library. Accepts a file object supplied by the client, a public image or video URL, a data URI, or base64 data. 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.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "autoposter_upload_media"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoOptional public image or video URL or data URI to upload into media library.
fileNoFile object supplied by the client (download_url, file_id, optional mime_type and file_name) for generated 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
    • changedInput schema / properties / file / description
      Previous value: -"File object provided by ChatGPT for AI-generated images or uploaded files."New value: +"File object supplied by the client (download_url, file_id, optional mime_type and file_name) for generated or uploaded files."
  2. 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"
      +}
  3. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true; the description adds concrete behavioral constraints — the 100MB chat download cap, the 5GB S3 path, and which input encodings are accepted. It does not cover what happens on name collisions, duplicates, or overwrites, which would matter for a mutation tool, so it stops short of full disclosure.

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?

Four sentences, each carrying distinct information: capability, accepted formats, size ceiling, and two escalation paths. The limit and the alternatives are front-loaded rather than buried, and there is no redundant restatement of the title or schema.

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 and full parameter coverage, the description only needs to explain intake constraints and routing, which it does thoroughly for size and source. It leaves gaps around duplicate handling and whether `name` affects storage paths, minor for an upload tool of this complexity.

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, but the description earns above baseline by clarifying that data URIs and base64 payloads are accepted and by characterizing the file object as client-supplied for generated or uploaded files. It does not clarify the precedence or mutual exclusivity between `url` and `file`, which an agent must infer.

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 enumerates the accepted input forms, so an agent knows exactly what operation this performs. It is clearly distinct from siblings like autoposter_get_media_upload_url and autoposter_create_upload_link, which it names.

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 routing rules with thresholds: use this tool up to the 100MB chat download limit, switch to a public URL or autoposter_get_media_upload_url for >100MB up to 5GB, and use autoposter_create_upload_link when the file lives only in chat or on the user's device. Both alternatives are named with the exact condition that selects them.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources