Skip to main content
Glama
Sign In

Socialync

by io.github.JackVitick
OverviewDiscussionsAdmin

delete_scheduled_post

DestructiveIdempotent

Cancel a pending scheduled post before it publishes. Pass a postId to cancel a single platform entry, or a groupId to cancel every platform in a grouped multi-platform post at once (the ids publish_scheduled returns together share a groupId). Destructive and not undoable -- show the user what will be cancelled and get explicit confirmation in chat first. If the user has switched on the publish confirmation dialog in Socialync settings (off by default) and their client supports MCP elicitation, Socialync also asks the user to confirm the cancellation in a dialog; a decline cancels nothing and comes back as success false with consent "declined"; no answer within 40 seconds counts as the chat confirmation. Already-published posts cannot be cancelled. Call get_scheduled_posts to find ids.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "delete_scheduled_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
postIdNoThe scheduled_posts id to cancel (one platform entry).
groupIdNoCancel every platform entry sharing this groupId (a whole grouped post). Takes precedence over postId.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the destructiveHint/idempotentHint annotations by disclosing that the action is not undoable, the elicitation consent flow (settings toggle, MCP elicitation support, 40-second timeout), and the exact failure shape ('success false with consent "declined"'). The 'not undoable' and 'destructive' claims are consistent with the annotations.

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?

Front-loaded with the core action and the two parameter modes, then layered detail on confirmation. Every sentence carries operational content, though the elicitation/timeout passage is dense enough that it slightly inflates the paragraph.

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?

For a destructive two-parameter tool with no output schema, the description covers the cancellation semantics, the confirmation requirement, the elicitation fallback behavior, and the published-post edge case. Nothing an agent needs to invoke it safely is missing.

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 the baseline is 3, but the description adds value by explaining that a postId is one platform entry while groupId cancels a whole grouped post, and that ids returned together by publish_scheduled share a groupId. It does not explicitly state that at least one of the two optional parameters must be supplied.

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?

States a specific verb and resource ('Cancel a pending scheduled post before it publishes') and immediately disambiguates the two modes of operation (single postId entry vs groupId grouped post). An agent can distinguish this from siblings like publish_scheduled or get_scheduled_posts without opening a schema.

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

Usage Guidelines5/5

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

Explicit preconditions and exclusions: must be pending and before publish, already-published posts cannot be cancelled, and 'Call get_scheduled_posts to find ids' names the sibling that supplies the required arguments. It also mandates a chat confirmation step before invocation.

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

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