Skip to main content
Glama

Zernio

by com.zernio

Post the same content to multiple platforms

posts_cross_post
Destructive

Post the same content to multiple platforms at once.

⚠️ 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" → Posts are saved but NOT published. User can edit them later.

IMMEDIATE MODE (publish_now=True) Use when user says: "publish now", "post now", "immediately" → Posts go live IMMEDIATELY on all platforms.

SCHEDULED MODE (default) Use when user says: "schedule", "programar", "in X hours" → Posts are scheduled for 1 hour from now.

⚠️ MULTI-ACCOUNT USERS:

  • To pick a specific account per platform, pass account_ids parallel to platforms (same order, comma-separated). Use empty string for a position to fall back to profile/auto-resolution.

  • To target multiple accounts of the SAME platform in one call, repeat the platform: platforms='twitter,twitter', account_ids='acc_a,acc_b'.

  • If you omit account_ids and the user has multiple accounts for any of the requested platforms, the tool errors with the candidate list - use it to retry.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contentYesThe post text/content (required)
is_draftNoSet to True to save as DRAFT (not published). Use when user wants to save without publishing Default: False.
platformsYesComma-separated list of platforms (e.g., 'twitter,linkedin,bluesky'). Repeat a platform to target multiple accounts of it: 'twitter,twitter'. (required)
media_urlsNoComma-separated URLs of media files to attach Default: .
profile_idNoScope auto-resolution to one profile when account_ids is empty. Default: .
account_idsNoComma-separated account IDs, parallel to `platforms`. Empty positions fall back to profile/auto-resolution. Required for multi-account users to disambiguate. Default: .
publish_nowNoSet to True to publish IMMEDIATELY to all platforms Default: False.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

TDQS

A4.3/5.0
Behavior4/5

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

Beyond destructiveHint=true, it explains that drafts stay unpublished, immediate posts go live on all platforms, the default schedule is one hour out, and multi-account resolution can fail with a candidate list. It does not explicitly state irreversibility or rate limits, but annotations already cover the destructive nature.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with scannable mode blocks and multi-account bullets, and the purpose is front-loaded. It is somewhat long, but most sentences carry necessary selection or retry behavior.

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?

For a 7-parameter cross-posting tool, the description is largely complete: required params are clear, mode behavior is specified, and multi-account errors are explained. The main caveat is that SCHEDULED MODE says 'in X hours' but actually schedules for 1 hour from now, which can mislead an agent.

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?

Schema coverage is 100%, and the description adds real meaning by tying is_draft and publish_now to mode selection and by explaining account_ids parallel ordering, empty-string fallback, and repeated platform names. It does not address conflicts like both is_draft and publish_now being true, which is a minor gap.

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 opening sentence states a concrete action and scope: 'Post the same content to multiple platforms at once.' This clearly distinguishes the tool from single-platform siblings like posts_create and posts_publish_now.

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 gives explicit intent-based triggers for draft, immediate, and scheduled modes, including user phrases and default behavior. It stops short of a 5 because it does not explicitly name sibling alternatives or state when not to use cross-posting.

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