SendIt

Get Scheduled Posts

get_scheduled_posts

Read-onlyIdempotent

List scheduled posts and their current status, including pending, publishing, TikTok draft-delivered, published, failed, or cancelled posts.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Optional forward-compatible maximum number of scheduled posts to return.
`cursor`	No	Optional forward-compatible pagination cursor from a previous scheduled-post listing response.
`status`	No	Optional forward-compatible status filter. Legacy handlers may continue returning pending posts only.
`endDate`	No	Optional forward-compatible upper date bound in YYYY-MM-DD format.
`team_id`	No	Team ID to list team's scheduled posts. If omitted, lists personal posts.
`platform`	No	Filter by platform (optional)
`upcoming`	No	Optional forward-compatible flag to prefer upcoming scheduled posts.
`startDate`	No	Optional forward-compatible lower date bound in YYYY-MM-DD format.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`posts`	No
`isError`	No
`success`	No
`postCount`	No
`schedules`	No
`errorMessage`	No
`followUpSuggestions`	No

Schema Changelog

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

Changed1 schema field changedMay 11, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "errorMessage": {
+      "type": "string"
+    },
+    "followUpSuggestions": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "isError": {
+      "type": "boolean"
+    },
+    "postCount": {
+      "type": "number"
+    },
+    "posts": {
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "schedules": {
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "success": {
+      "type": "boolean"
+    }
+  },
+  "type": "object"
+}

First observedMay 5, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is clear. The description adds a useful status list including 'TikTok draft-delivered', but does not mention pagination, team scope, or legacy handler caveats mentioned in the schema.

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?

A single, front-loaded sentence effectively communicates the core purpose and status coverage without redundant filler. Every word earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 8 optional parameters and an output schema, the description is minimal. It correctly identifies the core listing action but fails to signal important context like team_id, date-range filtering, platform filters, or pagination. These are documented in the schema, so the description is adequate but not comprehensive.

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 description coverage is 100%, and every parameter already has a detailed description and enums. The tool description adds no additional parameter semantics beyond restating the status enum, so the 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 clearly states the tool 'List scheduled posts' and enumerates the statuses it covers (pending, publishing, TikTok draft-delivered, published, failed, or cancelled). This specific verb+resource combination distinguishes it from singular get_scheduled_post and other post-management tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus siblings like get_scheduled_post, schedule_content, or list_calendar_events. The description gives no exclusions, alternative references, or contextual prerequisites.

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

All SendIt tools Inspect

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

Need Help?