Skip to main content
Glama
helbertparanhos

postforme-mcp-pro

create_media_upload_url

Generates a signed upload URL and corresponding media URL for later use in a post. Use this to upload media directly when you need control over the upload process.

Instructions

Get a signed URL to upload a media file. Returns an upload_url (PUT your bytes there) and the media URL to reference in a post. Prefer upload_media if you want the upload done for you in one step.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
content_typeNoMIME type of the file you'll upload (e.g. 'image/jpeg', 'video/mp4').
file_nameNoOptional original file name.
Behavior3/5

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

No annotations present; description explains the basic flow (returns upload_url and media URL, PUT bytes) but omits details like URL expiration, authentication needs, or size limits.

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?

Two concise sentences front-load the purpose, explain return values, and provide alternative tool guidance with no wasted words.

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?

Given no output schema, the description adequately covers return values and parameter usage, and contrasts with a sibling tool; lacks only minor details like URL expiry.

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% with clear descriptions; description adds no extra meaning beyond the schema for the two 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?

Description clearly states the verb 'get' and resource 'signed URL for uploading a media file', and distinguishes from sibling upload_media by noting it returns a URL for manual upload.

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?

Explicitly suggests preferring upload_media for one-step upload, but does not elaborate on when not to use this tool or potential pitfalls.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/helbertparanhos/postforme-mcp-pro'

If you have feedback or need assistance with the MCP directory API, please join our Discord server