Skip to main content
Glama
Sign In

Mondovo

by com.mondovo.app
OverviewDiscussionsAdmin

Add several posts to the content calendar

schedule_social_posts

Add up to 20 social posts to one brand's content calendar in ONE step and one approval — each exactly as schedule_social_post would add it (same fields per post, including video_project_id / video_asset_id and publish_to). A post WITH publish_to (or the shared top-level publish_to) is scheduled to publish publicly on those accounts at its day and time; one without is only a calendar plan. The posts are added one after another; one that is refused does not stop the others. The result lists every post by index (its position in posts, from 0) with ok, its post_id, scheduled_at, queued and video, or the error that stopped it, plus counts. Tell the user exactly which posts were scheduled and name every one that failed; never say a failed post was scheduled, and never say a video is on a post unless its video.attached is true. Free.

Input Schema

NameRequiredDescriptionDefault
postsYesThe posts, 1 to 20, each with the fields schedule_social_post takes.
brand_idYesBrand workspace id from list_brands
timezoneNoAn IANA time zone (e.g. Asia/Kolkata) ONLY when the owner named one. It is saved as the brand's time zone. Omit to use the brand's.
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.
publish_toNoConnection ids from list_social_accounts for every post that names no `publish_to` of its own. Omitted (and none on a post): that post is a calendar plan only.
fallback_timezoneNoThe owner's device time zone, used only when the brand has none on record.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / posts / items / properties / google
      Added value: +{
+  "additionalProperties": false,
+  "description": "Used when connection_ids names a Google Business Profile location; ignored otherwise.",
+  "properties": {
+    "button": {
+      "additionalProperties": false,
+      "properties": {
+        "action_type": {
+          "enum": [
+            "BOOK",
+            "ORDER",
+            "SHOP",
+            "LEARN_MORE",
+            "SIGN_UP",
+            "CALL"
+          ],
+          "type": "string"
+        },
+        "url": {
+          "description": "https link; not used for CALL (the listing phone).",
+          "format": "uri",
+          "type": "string"
+        }
+      },
+      "required": [
+        "action_type"
+      ],
+      "type": "object"
+    },
+    "event": {
+      "additionalProperties": false,
+      "description": "Required for EVENT and OFFER: the title and dates.",
+      "properties": {
+        "end_date": {
+          "description": "YYYY-MM-DD",
+          "type": "string"
+        },
+        "end_time": {
+          "description": "HH:MM",
+          "type": "string"
+        },
+        "start_date": {
+          "description": "YYYY-MM-DD",
+          "type": "string"
+        },
+        "start_time": {
+          "description": "HH:MM",
+          "type": "string"
+        },
+        "title": {
+          "maxLength": 58,
+          "type": "string"
+        }
+      },
+      "required": [
+        "title",
+        "start_date",
+        "end_date"
+      ],
+      "type": "object"
+    },
+    "offer": {
+      "additionalProperties": false,
+      "properties": {
+        "coupon_code": {
+          "maxLength": 58,
+          "type": "string"
+        },
+        "redeem_url": {
+          "format": "uri",
+          "type": "string"
+        },
+        "terms": {
+          "maxLength": 5000,
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "topic_type": {
+      "description": "STANDARD (an update), EVENT, or OFFER.",
+      "enum": [
+        "STANDARD",
+        "EVENT",
+        "OFFER"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "topic_type"
+  ],
+  "type": "object"
+}
    • changedInput schema / properties / posts / items / properties / platform / enum
      Previous value: -[
-  "instagram",
-  "linkedin",
-  "facebook",
-  "x",
-  "tiktok",
-  "youtube_shorts"
-]New value: +[
+  "instagram",
+  "linkedin",
+  "facebook",
+  "x",
+  "tiktok",
+  "youtube_shorts",
+  "google_business"
+]
  2. 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"
+}
  3. Added

TDQS

A4.6/5.0
Behavior5/5

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

Well beyond the annotations, it discloses the partial-failure contract ('the posts are added one after another; one that is refused does not stop the others'), the exact result shape keyed by `index`/`ok`/`post_id`/`queued`/`video`/`error`, and that the call is free. The annotations only cover write/open-world/non-idempotent; the batch semantics and per-item outcome reporting are genuinely new information.

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 purpose and the 20-post limit are front-loaded, and the later sentences on partial failure and reporting duties each carry distinct operational weight. It is a single dense paragraph, though, and the closing instruction about naming failures is advisory guidance rather than tool behavior, which loosens the structure slightly.

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 job of describing the return payload and does so concretely, including the `video.attached` check an agent needs to avoid false claims. Combined with the partial-failure contract and the cost note, an agent has everything needed to invoke it and report results correctly.

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 a 3 is the floor, but the description adds real meaning on top: the top-level `publish_to` acts as a default for posts that omit it, and `video_project_id`/`video_asset_id`/`publish_to` are named as the fields controlling attachment and publishing. It stops short of explaining the timezone fallback parameters, which are left entirely 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?

The opening sentence states a specific verb, resource and hard scope limit: 'Add up to 20 social posts to one brand's content calendar in ONE step and one approval.' It explicitly positions itself against the single-post sibling ('each exactly as schedule_social_post would add it'), so an agent can pick it out of a large calendar toolkit without opening the schema.

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?

It gives a clear selection rule between the two behaviors an agent must distinguish: a post with `publish_to` is scheduled to publish, one without is only a calendar plan. It also points to `list_social_accounts` for connection ids. It never states the inverse routing ('use schedule_social_post when you have a single post'), so the alternative is only implied rather than spelled out.

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