Skip to main content
Glama

Zernio

by com.zernio

Create a social media post (draft, scheduled, or immediate)

posts_create
Destructive

Create a social media post. Can be saved as DRAFT, SCHEDULED, or PUBLISHED immediately.

⚠️ IMPORTANT - Choose the correct mode based on user intent:

DRAFT MODE (is_draft=True) Use when user says: "draft", "borrador", "save for later", "don't publish", "save it", "guardar" → Post is saved but NOT published and NOT scheduled. User can edit it later.

IMMEDIATE MODE (publish_now=True) Use when user says: "publish now", "post now", "publica ya", "immediately", "right now", "ahora" → Post goes live IMMEDIATELY.

SCHEDULED MODE (default) Use when user says: "schedule", "programar", "in X minutes/hours", "at 3pm", "tomorrow" → Post is scheduled for future publication. Use schedule_minutes to set the delay.

⚠️ MULTI-ACCOUNT USERS (agencies, multi-client setups): If the user has more than one account on the target platform, you MUST pass account_id. Call accounts_list (or profiles_list then accounts_list) first to discover the right ID. If you omit account_id when multiple accounts exist, the tool returns an error listing the candidates - use it to retry.

Examples:

  • "Create a draft tweet" → is_draft=True

  • "Post this to Twitter now" → publish_now=True

  • "Schedule a LinkedIn post for 2 hours from now" → schedule_minutes=120

  • "Post this to Acme's Twitter" → call accounts_list, find Acme's twitter ID, pass account_id

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleNoPost title (required for YouTube, recommended for Pinterest) Default: .
contentYesThe post text/content (required)
is_draftNoSet to True to save as DRAFT (not published, not scheduled). Use when user wants to save without publishing Default: False.
platformYesTarget platform: twitter, instagram, linkedin, tiktok, bluesky, facebook, youtube, pinterest, threads (required)
account_idNoSpecific account ID to post from. REQUIRED when the user has multiple accounts on this platform. Call accounts_list first to find IDs. Leave empty only if there is exactly one account for this platform. Default: .
media_urlsNoComma-separated URLs of media files to attach (images, videos) Default: .
profile_idNoScope account resolution to one profile (e.g. one client in an agency setup). Use when account_id is unknown but the target profile is. Call profiles_list to find IDs. Default: .
publish_nowNoSet to True to publish IMMEDIATELY. Post goes live right now Default: False.
schedule_minutesNoMinutes from now to schedule. Only used when is_draft=False AND publish_now=False Default: 60.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

TDQS

A4.7/5.0
Behavior5/5

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

The description adds real behavioral context beyond annotations: draft posts are saved but not published/scheduled, immediate mode goes live right away, scheduled mode publishes later, and omitted account_id triggers a recoverable error listing candidates. This is strong transparency and does not contradict the annotations.

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 structure is exemplary: a short top-level summary, mode-specific headers, bolded parameter names, explicit Spanish/English usage phrases, and examples with minimal redundancy. It is long, but every block earns its place by resolving a high-stakes ambiguity for a 9-parameter tool.

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?

Given the complexity of 9 parameters, a multi-account pitfall, and schema coverage, this description gives enough to avoid the most common failures: mode confusion, missing account_id, and scheduling semantics. It covers recovery from error, and the output schema exists, so the description does not need to explain return values.

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?

All parameters are already documented in the schema, so the baseline is 3. The description adds extra value by explaining the interplay between is_draft, publish_now, schedule_minutes, account_id, and profile_id via concrete user phrases and examples, therefore lifting it above baseline.

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 title and description clearly state the tool creates a social media post and identifies the three possible states (draft, scheduled, immediate). This distinctively differentiates it from sibling tools like posts_publish_now, posts_edit_post, and posts_list by emphasizing the create-and-mode-selection behavior.

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 tool gives explicit, thoughtful usage guidance by tying specific user phrases to each mode and requiring account_id discovery via accounts_list for multi-account users. It lacks an explicit 'not this tool' statement for neighboring create-related siblings like posts_cross_post or posts_publish_now, so it is clear but not fully exclusionary.

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

All Zernio toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

C2.7/5.0
Disambiguation3/5

Many tools are clearly separated by domain prefix, but several overlap: posts_publish_now duplicates posts_create's publish_now mode, posts_edit_post vs posts_update is confusing without reading both descriptions, and analytics_get_analytics broadly overlaps the more specific analytics metrics tools. The descriptions do help disambiguate, but the large number of similar post/analytics helpers still creates selection risk.

Naming Consistency3/5

Most tools follow a readable lower_snake resource_verb format, with domains like accounts_, posts_, profiles_, and queue_. However, there is notable drift: redundant suffixes (queue_create_queue_slot, tracking_tags_get_tracking_tag_stats), singular/plural mismatch (account_groups_ vs accounts_), non-prefixed helpers (call_tool, search_tools, docs_search), and paired verbs that seem arbitrary (posts_edit_post vs posts_update). It is readable but not cleanly consistent.

Tool Count2/5

51 tools is far above the range where an agent can quickly select the right one, and many entries are wrappers or variants: publish_now, edit_post, retry_all_failed, and multiple analytics/queue helpers could be consolidated. The broad domain justifies more tools than a tiny server, but this count is excessive and will add navigation overhead.

Completeness4/5

The server covers the core social media management lifecycle well: profiles, accounts, posts, scheduling, queueing, analytics, comments, mentions, media uploads, tracking tags, and usage billing are all represented. There are minor gaps—tracking tags are read-only, there is no direct account connection/disconnection flow, and published-post deletion is unsupported—but agents can complete the main workflows with these tools.

Resources