Skip to main content
Glama
Sign In

Mondovo

by com.mondovo.app
OverviewDiscussionsAdmin

Where did a post go?

get_post_publish_status
Read-onlyIdempotent

For one post: every account it is queued to, with its state (queued, published, failed, needs_reconnect, needs_attention…), the live link once published, why it failed or is waiting, and the next retry. Use it for "did it go out?", "what's the link?" and "why did it fail?". Read-only and free.

Input Schema

NameRequiredDescriptionDefault
post_idYesThe post id from get_calendar
brand_idYesBrand workspace id from list_brands
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.

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. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds genuinely new context: the call is "free" (no credit spend) and the state vocabulary it can report (queued, published, failed, needs_reconnect, needs_attention), plus that a next-retry time is included. It does not cover auth requirements or fresh-vs-cached data, keeping it short of a 5.

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?

Front-loads scope in the first clause, then enumerates returned fields, then gives trigger phrases, then a one-line cost/safety note. No filler, and every sentence carries usable information.

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?

There is no output schema, so the description must describe returns — and it does, naming each field an agent would need (per-account state, link, failure reason, next retry). It could say more about ordering or whether accounts with no queue entry appear, but nothing essential is missing.

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 coverage is 100%, so both required ids and the optional user_goal are already documented in the schema with sourcing hints (from get_calendar, from list_brands). The description adds only that the post is singular ("for one post"), which is baseline-level value.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ("for one post: every account it is queued to") and enumerates exactly what is returned — per-account state, live link, failure reason, next retry. Scope is unambiguous and separable from sibling get_post_performance, though that sibling is never named.

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 three concrete user-intent phrasings ("did it go out?", "what's the link?", "why did it fail?") that map cleanly onto when to call it. No explicit exclusion against get_post_performance or cancel_queued_post/reschedule_social_post, so an agent still has to infer those boundaries.

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