Skip to main content
Glama
Sign In

Mondovo

by com.mondovo.app
OverviewDiscussionsAdmin

Publish several posts to social accounts

queue_week_for_publishing
Idempotent

PUBLISHES several planned posts PUBLICLY to the same named social accounts, each at its own scheduled time (up to 14). Nothing is moved. Name every account by its connection_id from list_social_accounts — there is no default and it never goes to all connected accounts. Free (no Creative Credits). One post that cannot go does not stop the others; the result lists queued and refused posts, and skips (lists as skipped, never publishes) any post whose time has already passed.

Input Schema

NameRequiredDescriptionDefault
brand_idYesBrand workspace id from list_brands
post_idsYesPost ids from get_calendar
timezoneNoThe owner's IANA timezone, when they named one.
user_goalNoOptional: the user's goal behind this call, in one short sentence of plain words (e.g. "add a page so customers can book tables"). No names, emails or other personal details.
connection_idsYesThe accounts to publish to: each account's connection_id from list_social_accounts, as the user chose them. Required — there is no default.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / user_goal
      Added value: +{
+  "description": "Optional: the user's goal behind this call, in one short sentence of plain words (e.g. \"add a page so customers can book tables\"). No names, emails or other personal details.",
+  "type": "string"
+}
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover safety (readOnly=false, destructive=false, idempotent=true, openWorld=true), yet the description adds real behavioral context: publishing is public, nothing is moved, the call is free of Creative Credits, and one failure does not abort the batch. The partial-success semantics (queued/refused/skipped) and the skip rule for past times are exactly the kind of detail an agent cannot infer from annotations.

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?

A single dense paragraph that front-loads the action and its scope, then layers constraints in order of importance. Every clause carries information, though the em-dash and parenthetical asides make it slightly harder to scan than a short bulleted form would be.

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?

With no output schema, the description takes on the burden of describing the result (lists of queued, refused, and skipped posts) and does so. Combined with the failure-isolation, past-time, and account-default rules, an agent has everything needed to call this correctly and interpret the outcome.

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%, so the baseline is 3, and the description clears it by explaining the connection_ids contract (source tool, no default, never all accounts) and the 14-post ceiling on post_ids. It adds intent-level meaning rather than restating field types, though brand_id and the optional timezone/user_goal fields are left to the schema.

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?

Opens with a specific verb and resource ('PUBLISHES several planned posts PUBLICLY') and immediately scopes it: same named accounts, each at its own scheduled time, up to 14 posts. That distinguishes it from the singular queue_post_for_publishing and from schedule_social_post without the agent needing to compare schemas.

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?

Gives clear operating conditions: accounts must be named via connection_id from list_social_accounts, there is no default, and past-dated posts are skipped. It does not explicitly name when to prefer this over queue_post_for_publishing or schedule_social_posts, so the sibling routing is only implied by 'several'.

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

All Mondovo toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources