Skip to main content
Glama

SendIt

by io.github.Shree-git

Bulk Update Calendar Events

bulk_update_calendar_events

Apply one bulk action to many calendar events at once, including shifts, explicit reschedules, queue moves, cancellations, or assignments.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idsYesCalendar event IDs or scheduled post IDs to update.
shiftNo
actionYesBulk action to apply.
team_idNoTeam ID to operate in team scope. Get available teams with list_teams. If omitted, uses personal scope.
timezoneNoOptional IANA timezone for queue-based moves.
applyScopeNoWhether to affect only the selected IDs or their recurrence groups.
assigneeIdNoRequired for the 'assign' action.
scheduledAtNoReplacement ISO 8601 time for the 'set_time' action.
deltaMinutesNoCompatibility shift amount in minutes.
scheduledTimeNoCompatibility alias for scheduledAt.

Schema Changelog

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

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already provide readOnly/destructive hints; the description adds the list of action categories but does not disclose partial-failure behavior, recurrence scope implications, or side effects beyond the action list. It does not contradict 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 efficiently communicates the core purpose without filler or redundancy.

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?

Despite having 10 parameters and no output schema, the description stays minimal. It doesn't address important contextual aspects like the 200-item cap, potential partial failures, or behavior of actions that require additional fields (e.g., assign). The rich schema compensates somewhat, but the description could provide more high-level guidance.

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 high (90%), so parameters are well-documented. The description adds no syntax or constraint details beyond what the schema provides, only mapping the action list. It meets the baseline without adding parameter-specific value.

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 performs a single bulk action across many calendar events, enumerating specific action types (shifts, reschedules, queue moves, cancellations, assignments). This distinguishes it from single-event update_calendar_event and bulk_schedule.

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 phrase 'many calendar events at once' implies the use case for bulk operations, contrasting with single-event tools. However, it does not explicitly mention when not to use it or point to alternatives like update_calendar_event for individual updates.

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