Skip to main content
Glama

Social0

upload_media

Upload an image or video to Social0 and get a media ID for posts. For remote AI hosts (Claude.ai, ChatGPT), pass url (public direct file URL) or data (base64). file_path only works when the MCP server can read that path on its own machine.

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": "upload_media"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoPublic http(s) URL to download. Must be a direct file link the server can fetch.
dataNoBase64 file bytes or a data: URL (data:image/png;base64,...).
filenameNoFilename with extension (required for bare base64 data; optional for url).
file_pathNoLocal path on the MCP server machine. Do not use for remote sandboxes.
mime_typeNoMIME type if not clear from filename/url (e.g. image/png).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and closed-world, so the safety profile is covered. The description adds value beyond that by disclosing the return artifact (media ID for posts) and the host-environment constraint that determines which parameters actually work. It stops short of saying whether re-uploading the same file creates duplicates, which matters given idempotentHint=false.

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?

Three short sentences with the purpose and return value front-loaded, followed by the environment caveat. The telegraphic style ('pass url ... or data') is efficient rather than confusing, and no sentence is filler.

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?

Covers purpose, output artifact, and the remote-vs-local constraint for a 5-parameter, zero-required tool with no output schema. The one gap is that it never states that at least one of url, data, or file_path must actually be supplied, which is not obvious from a schema where nothing is required.

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 baseline is 3, but the description adds host-context meaning that the schema does not: url/data are the viable paths for remote sandboxes while file_path requires server-local filesystem access. That framing directly changes how an agent picks between three otherwise-similar-looking source parameters.

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 ('Upload an image or video to Social0') plus the concrete outcome ('get a media ID for posts'), which tells an agent exactly what it produces. No sibling tool in the catalog uploads media, so the purpose is unambiguous without needing differentiation.

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?

Gives explicit conditional guidance on which input channel to use: url/data for remote AI hosts, file_path only when the MCP server can read the local path. It does not discuss ordering relative to publish_post/schedule_post or what to do if upload fails, but the transport-selection guidance is the key decision an agent faces here.

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.