Skip to main content
Glama
RobinCouet

@start-win/social-mcp

by RobinCouet

Uploader un média

upload_media

Upload an image or video temporarily to obtain a file name for use in publishing or scheduling posts.

Instructions

Upload temporaire d'une image ou vidéo (~20 min). Retourne tempFileName à passer dans publish_post ou schedule_post.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoNom du fichier, ex. photo.jpg
typeNoType MIME, ex. image/jpeg
filePathNoChemin local du fichier (prioritaire si fourni)
contentBase64NoContenu base64 (si filePath absent)
Behavior3/5

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

No annotations provided, so description carries full burden. Discloses the temporary nature (~20 min) but does not mention file deletion after expiration, authentication needs, or error behavior. Adequate but could add more context.

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 sentences, no wasted words, front-loaded with purpose. Highly efficient and easy to parse.

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 low complexity, schema covers params, and description explains the output and time constraint. Nearly complete; could mention size limits or error cases but not necessary for basic tool.

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 description coverage is 100%, so schema already documents all 4 parameters. Description adds no additional parameter semantics beyond the output explanation. Baseline 3 is appropriate.

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 it uploads a temporary image/video and returns a tempFileName for use in publish_post or schedule_post. Distinguishes from sibling tools by specifying its role as a prerequisite 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?

Explains that the upload is temporary (~20 min) and the returned tempFileName is intended for publish_post or schedule_post. Provides clear context but lacks explicit when-not-to-use guidance or alternatives.

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/RobinCouet/social-mcp'

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