Skip to main content
Glama
FirstReply MCP Server

FirstReply MCP Server

Official
by FirstReply

Post Media Upload

post_media_upload

Upload an image or video from a public HTTPS URL and return its media ID for post creation or scheduling; the address must report the file size.

Instructions

Upload an image or video for a post from a public https address (JPEG, PNG, WebP or GIF, MP4 or MOV, up to 1 GB; the address has to report the file size). Returns the media with its id: pass it as media to post_create or post_schedule. An upload no post uses is removed after a while.

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": {
      "organizationId": "<organizationId>",
      "url": "<url>"
    },
    "name": "post_media_upload"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPublic https:// address of the file. Private or local addresses are refused.
fileNameNoFile name to keep. Default: the last part of the address.
durationMsNoVideos: the length in milliseconds, when known. The checks for Shorts and Reels use it.
contentTypeNoMIME type, e.g. image/jpeg or video/mp4. Default: what the address reports.
organizationIdYesThe organization id. Use organization_list to find it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.0

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations (readOnly=false, openWorld=true, idempotent=false), the description discloses concrete operational constraints the agent cannot infer: accepted formats, the 1 GB ceiling, the requirement that the address report file size, and that unused uploads are garbage-collected. It also states the return payload ('the media with its id'), which matters because no output schema exists.

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?

Three dense sentences with zero filler: capability and constraints first, return value second, lifecycle caveat last. Every clause carries information an agent needs to call the tool correctly.

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?

For a five-parameter mutation tool with no output schema, the description covers what is uploaded, what is rejected, what comes back (media id), how the id is consumed, and what happens to abandoned uploads. Nothing essential to a correct call is missing.

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 coverage is 100%, so all five parameters are already documented, including url, fileName, durationMs, contentType, and organizationId. The description adds only the file-size-reporting requirement for the address, which is a marginal gain; it says nothing extra about durationMs or contentType beyond what the schema states.

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 opens with a specific verb and resource ('Upload an image or video for a post') and immediately scopes it to a 'public https address', which distinguishes it from the write/publish siblings post_create and post_schedule. An agent knows this is the media-staging step, not the publishing step.

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 explicitly states the downstream usage: 'pass it as media to post_create or post_schedule', which tells the agent where this fits in the workflow, and the orphan-cleanup note implies you should upload close to publishing. It stops short of an explicit when-not-to-use or a statement about reusing an existing media id instead of re-uploading.

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

Deploy Server

Other Tools