Skip to main content
Glama
AdaptlyPost

AdaptlyPost

Official

Delete Recurring Post

delete_recurring_post
DestructiveIdempotent

Permanently removes a recurring post series and cancels its next scheduled post while keeping already published posts; use delete_post to skip a single date instead.

Instructions

Delete a recurring post: the series stops for good and its upcoming SCHEDULED post is deleted. Posts that already went out are kept. Prefer pause_recurring_post when the user may want the series back. To skip a single date, delete that occurrence with delete_post instead; the series continues. Ids outside the workspace (the current one unless workspaceId names another) return "Recurring post not found". Returns { deleted: true }. Irreversible.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

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

Input Schema

NameRequiredDescriptionDefault
idYesRecurring post ID to delete, from list_recurring_posts
workspaceIdNoWorkspace to act in: an id from list_workspaces. Omit to act in the workspace list_workspaces marks current. Use the same workspaceId for every call about the same workspace, since ids from one workspace (accounts, posts, uploads) do not exist in another

Output Schema

NameRequiredDescriptionDefault
resultYesAn object with deleted: true once the recurring post is removed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.22.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the low bar is cleared; the description still goes further by stating exactly what is destroyed (the upcoming scheduled post), what survives ('Posts that already went out are kept'), that the action is irreversible, and the exact failure text for foreign ids ('Recurring post not found'). That is unusually complete mutation-behavior disclosure.

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?

Effect (permanent stop, scheduled post deleted, sent posts kept) is front-loaded, followed by sibling routing, then edge-case error behavior. Every sentence carries distinct information and nothing is repeated from the annotations or schema verbatim.

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?

The tool is a destructive single-object mutation with two fully documented parameters and an output schema, so return-value detail is not required; the description still notes '{ deleted: true }' for convenience. Nothing an agent needs to call it safely and correctly 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; the description earns above that by explaining the consequence of workspace scoping, namely that ids outside the acting workspace fail with 'Recurring post not found'. It does not add format or syntax detail beyond the schema for either parameter.

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 opens with a specific verb+resource ('Delete a recurring post') and immediately scopes the effect: the series stops permanently and only the upcoming SCHEDULED post is removed. That scope statement is what separates it from pause_recurring_post and delete_post, which it also names explicitly, so an agent can disambiguate without opening another 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?

It gives conditional routing rather than bare alternatives: prefer pause_recurring_post 'when the user may want the series back', and use delete_post 'to skip a single date' because the series continues. The workspace caveat ('the current one unless workspaceId names another') adds a further usage rule for multi-workspace calls.

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

Deploy Server

Other Tools