Skip to main content
Glama
AdaptlyPost

AdaptlyPost

Official

Pause Recurring Post

pause_recurring_post
DestructiveIdempotent

Pause a recurring post to stop future occurrences and remove its upcoming scheduled post until resumed; published posts stay, and slots missed while paused are skipped.

Instructions

Pause a recurring post: it stops creating occurrences and deletes its upcoming SCHEDULED post, preventing future scheduled occurrences until resume_recurring_post; an occurrence already publishing may still complete. Posts already published are kept. Slots that pass while paused are skipped, never published later. Use it when the user wants to hold the series; use delete_recurring_post to stop it for good. Deleting only the upcoming post with delete_post skips that one date and the series continues. Ids outside the workspace (the current one unless workspaceId names another) return "Recurring post not found". Returns the recurring post with status PAUSED and pauseReason USER.

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": "pause_recurring_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesRecurring post ID to pause, 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
resultYesThe paused recurring post: id, status PAUSED, pauseReason USER, the schedule, occurrenceCount, and the content and platforms.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.22.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true, but the description goes well beyond them: an in-flight occurrence may still complete, published posts are kept, skipped slots are never back-published, and the specific error string for out-of-workspace ids. It also names the returned state (status PAUSED, pauseReason USER), which the agent cannot infer from hints alone.

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 ordered from effect to alternatives to error/return behavior. It is dense but slightly repetitive in the opening clause ('stops creating occurrences... preventing future scheduled occurrences'), and the multi-alternative routing adds length, though most of it earns its place.

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, idempotent mutation with an output schema, this covers effects, reversibility path (resume_recurring_post), timing edge cases, failure mode, and resulting state. An agent has everything needed to decide and call correctly.

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 baseline would be 3; the description adds meaning by explaining that ids outside the acting workspace fail with 'Recurring post not found' and clarifying the current-workspace default for workspaceId. That is genuine value beyond the schema text, though it does not document the id parameter's source further.

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?

Opens with a specific verb+resource ('Pause a recurring post') and immediately defines what pausing means mechanically: stops creating occurrences and deletes the upcoming SCHEDULED post. It explicitly differentiates itself from delete_recurring_post and delete_post, so an agent can distinguish it from siblings without reading any 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?

States exactly when to use it ('when the user wants to hold the series') and pairs each alternative with the condition that selects it: delete_recurring_post to stop for good, delete_post to skip a single date while the series continues. This is explicit when/when-not/alternatives coverage.

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