Skip to main content
Glama
AdaptlyPost

AdaptlyPost

Official

Resume Recurring Post

resume_recurring_post
Destructive

Restart a paused recurring post so it publishes future occurrences. Only slots after now are scheduled; missed ones are skipped, and the series stays ended if no slots remain.

Instructions

Resume a PAUSED recurring post. It continues from the next occurrence after now; slots missed while paused are not published. The next occurrence is created as a SCHEDULED post about 24 hours before it goes out and then publishes to the networks, so confirm with the user first. If the series has no slot left (endsOn passed or maxOccurrences reached) it comes back ENDED instead. When pauseReason is CONNECTION_REMOVED, ACCESS_LOST, SUBSCRIPTION_INACTIVE or INVALID_CONTENT, fix the cause first or the series pauses again. Ids outside the workspace (the current one unless workspaceId names another) return "Recurring post not found". Returns the recurring post with its new status and nextOccurrenceAt.

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

Input Schema

NameRequiredDescriptionDefault
idYesRecurring post ID to resume, 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 resumed recurring post: id, status (ACTIVE, or ENDED when no slot is left), nextOccurrenceAt, the schedule, occurrenceCount, and the content and platforms.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.22.0

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, but the description goes well beyond that: it explains missed slots are not published, that a SCHEDULED post is generated ~24h before publishing, that the series can come back ENDED, and that it re-pauses if the underlying cause isn't resolved. That is exactly the side-effect detail an agent needs before invoking a destructive mutation.

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?

Front-loaded with the action, then ordered by decision relevance: continuation semantics, the confirmation warning, the terminal-state case, the pause-cause remediation, and the scoping error. Every sentence conveys operational information; nothing is filler.

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, non-idempotent mutation this covers preconditions, side effects, failure/terminal outcomes, remediation of pause reasons, cross-workspace scoping, and the shape of the response. With an output schema present and 100% parameter coverage, no gap remains that would cause a misinvocation.

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 100%, so both id and workspaceId are already fully documented, including where the id comes from. The description only adds one piece of meaning beyond the schema: that ids outside the resolved workspace return 'Recurring post not found'. Baseline 3 is appropriate when the schema carries the detail.

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 and resource plus a precondition: 'Resume a PAUSED recurring post.' The agent immediately knows the operation and the state the target must be in, which cleanly separates it from pause_recurring_post or delete_recurring_post without needing schemas.

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?

Gives real when-to-use context (only for paused series), a required confirmation step ('confirm with the user first'), and when-not conditions: if the series has no slot left it returns ENDED, and if pauseReason is CONNECTION_REMOVED/ACCESS_LOST/SUBSCRIPTION_INACTIVE/INVALID_CONTENT the cause must be fixed first. It doesn't explicitly name a sibling alternative, which keeps it short of a 5.

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