Skip to main content
Glama
RobinCouet

@start-win/social-mcp

by RobinCouet

Programmer un post

schedule_post

Schedule posts to Facebook, Instagram, LinkedIn, X, Google, and TikTok for future dates. Instagram and TikTok require media.

Instructions

Programme un post pour une date future (ISO 8601, min. 2 min, max. 90 jours). Instagram et TikTok exigent un média.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesContenu du post
mediaNo
networksYesRéseaux cibles
scheduledAtYesDate de publication ISO 8601, ex. 2026-06-20T09:00:00+02:00
perNetworkTextNo
perNetworkScheduleNoDate différente par réseau, ex. { "linkedin": "2026-06-20T09:00:00+02:00" }
Behavior3/5

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

With no annotations, the description discloses timing constraints and network-specific media requirements, but omits important traits like reversibility (hinted by sibling 'cancel_scheduled_post'), error handling, or what happens on validation failure.

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?

The description is two sentences, front-loaded with the main purpose, and contains no redundant words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema and 6 parameters with nested objects, the description lacks details on return values, prerequisites (e.g., connected networks), and per-network overrides, making it only partially complete.

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?

The schema covers 67% of parameters; the description adds value by specifying min/max delay for 'scheduledAt' and media necessity for specific networks, going beyond the schema's basic examples.

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 uses a specific verb ('Programme' / schedules) and resource ('post'), and clearly distinguishes the tool from siblings like 'publish_post' by focusing on future dating.

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?

The description provides clear constraints (ISO 8601, min 2 min, max 90 days, media required for Instagram/TikTok), but does not explicitly state when not to use it or mention alternatives like 'publish_post' for immediate publishing.

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