Skip to main content
Glama

SendIt

by io.github.Shree-git

Trigger Scheduled Post

trigger_scheduled_post

Manually trigger a scheduled post to publish immediately.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
team_idNoTeam ID to operate in team scope. Get available teams with list_teams. If omitted, uses personal scope.
scheduleIdYesThe ID of the scheduled post to trigger

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
isErrorNo
resultsNo
successNo
errorMessageNo
totalPlatformsNo
followUpSuggestionsNo
successfulPlatformsNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "errorMessage": {
+      "type": "string"
+    },
+    "followUpSuggestions": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "isError": {
+      "type": "boolean"
+    },
+    "results": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "error": {
+            "type": "string"
+          },
+          "platform": {
+            "enum": [
+              "x",
+              "linkedin",
+              "linkedin-page",
+              "facebook",
+              "instagram",
+              "threads",
+              "bluesky",
+              "mastodon",
+              "nostr",
+              "youtube",
+              "tiktok",
+              "lemmy",
+              "discord",
+              "slack",
+              "telegram",
+              "pinterest",
+              "dribbble",
+              "devto",
+              "hashnode",
+              "gmb",
+              "whop",
+              "producthunt"
+            ],
+            "type": "string"
+          },
+          "postId": {
+            "type": "string"
+          },
+          "postUrl": {
+            "type": "string"
+          },
+          "success": {
+            "type": "boolean"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "success": {
+      "type": "boolean"
+    },
+    "successfulPlatforms": {
+      "type": "number"
+    },
+    "totalPlatforms": {
+      "type": "number"
+    }
+  },
+  "type": "object"
+}
  2. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already convey that this is a non-read-only, non-idempotent mutation. The description adds the 'publish immediately' side effect, but it does not disclose potential irreversible consequences or external platform effects beyond what openWorldHint hints at. No contradiction with 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 description is a single, front-loaded sentence that states the action and result without any redundant detail. It is appropriately brief for a simple tool.

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?

The tool has a clear purpose, a simple parameter set (one required), and an output schema exists, so return values are presumably documented. While error scenarios (e.g., schedule not found) are not mentioned, the description is adequate for a tool of this complexity.

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 descriptions cover 100% of the parameters, including team_id's scope semantics and scheduleId's purpose. The tool description adds no additional parameter-level meaning, so baseline 3 is appropriate.

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 description uses a specific verb ('trigger') and resource ('scheduled post') along with the immediate outcome ('publish immediately'), making the action unambiguous. It clearly distinguishes this from scheduling, editing, or deleting a post.

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 implies a clear use case: manually publishing a scheduled post ahead of its scheduled time. It does not explicitly exclude alternatives like retry_scheduled_post, but the context is understandable without needing additional guidance.

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

All SendIt 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

B3/5.0
Disambiguation2/5

With 148 tools, there is significant overlap. For example, generate_content, publish_ai, generate_post_bundle, and request_project_content all generate content; get_analytics, get_unified_analytics, get_post_analytics, get_ad_performance, and get_unified_ad_report all fetch performance metrics; and list_inbox vs list_conversations blur comment and conversation management. Descriptions help, but boundaries between tools are often unclear.

Naming Consistency3/5

Most tools follow a verb_noun pattern (e.g., list_teams, create_goal, delete_post), but there are notable deviations: create_library_item vs save_to_library, publish_content vs publish_ai, schedule_content vs schedule_content_advanced, and connect_platform vs connect_connector. Mixed prefixes like 'autopilot_', 'check_', and 'get_' are fine, but overlapping verbs and a hyphen in 'connect_linkedin-page' reduce consistency.

Tool Count1/5

148 tools is extreme for any server. Even for a broad social media management platform, this is far beyond what an agent can effectively navigate. The count is unwieldy and suggests the surface should be split into multiple focused servers (publishing, analytics, connectors, workflows, etc.).

Completeness3/5

The core social publishing workflow is well covered (create, schedule, publish, edit, delete, retry), and there are extensive features for analytics, workflows, connectors, and AI agents. However, some resources have CRUD gaps: no update/delete for brand voices, no delete_project, no update/delete for Product Hunt goals, and no explicit get_workflow. These are workable but notable omissions.

Resources