Skip to main content
Glama
AdaptlyPost

AdaptlyPost

Official

List Recurring Posts

list_recurring_posts
Read-onlyIdempotent

Lists recurring post series in a workspace, filtered by ACTIVE, PAUSED or ENDED status, with pagination plus next occurrence and pause reasons to check schedules or find why a series stopped.

Instructions

List the recurring posts (series) in the workspace (the current one unless workspaceId names another), created by passing recurrence to create_post. Returns { recurringPosts, total, hasMore }; each series has id, status (ACTIVE, PAUSED or ENDED), pauseReason when paused, frequency, interval, weekdays, startsAt, timezone, endsOn or maxOccurrences, nextOccurrenceAt, occurrenceCount, and the content and platforms every occurrence copies. Only the next occurrence of an ACTIVE series exists as a SCHEDULED post, created about 24 hours ahead; list_posts shows it with recurringPostId set. A series pauses itself after 3 failed posts in a row, when the subscription lapses, when its creator loses workspace access, when one of its accounts is disconnected, or when a platform rejects the content; pauseReason and lastError say which. Page with offset while hasMore is true. Editing a series or skipping one date is only possible in the AdaptlyPost app.

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

Input Schema

NameRequiredDescriptionDefault
limitNoRecurring posts per page
offsetNoRecurring posts to skip; increase by limit while hasMore is true
statusesNoFilter by status (e.g. ["ACTIVE", "PAUSED"]); omit for all statuses
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 recurringPosts (each with id, status, pauseReason, lastError, frequency, interval, weekdays, startsAt, timezone, endsOn, maxOccurrences, nextOccurrenceAt, occurrenceCount, contentType, text, mediaUrls, platformTypes, and platforms), total (count of all matches), and hasMore.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.22.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly/ idempotent/ non-destructive, yet the description still adds substantive behavior: the auto-pause triggers (3 consecutive failures, lapsed subscription, lost workspace access, disconnected account, platform rejection), the pauseReason/lastError diagnostic fields, and the 24-hour-ahead scheduling model. It doesn't cover rate limits or ordering of returned series, which keeps it just shy of a 5.

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?

Purpose and scope are front-loaded in the first clause and each subsequent sentence carries real information. The long enumeration of series fields (id, status, frequency, interval, weekdays, startsAt, timezone, endsOn, nextOccurrenceAt, occurrenceCount...) partially duplicates the output schema and could be trimmed without losing meaning.

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 read-only filtered-list tool with an output schema, four fully documented parameters and rich annotations, the description covers the remaining gaps an agent needs: what a series is relative to a scheduled post, the status vocabulary, why a series would be paused, and how to page. Nothing essential to correct invocation is missing.

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 description coverage is 100%, including the offset paging loop and the workspaceId scoping rule, so the baseline is 3. The description restates rather than extends these — "Page with offset while hasMore is true" duplicates the offset description and workspaceId handling is repeated nearly verbatim, adding no new meaning such as a maximum reasonable limit or status-filter interaction.

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?

Specific verb and resource ("List the recurring posts (series) in the workspace"), plus the origin story ("created by passing recurrence to create_post") and an explicit contrast with the sibling list_posts, which shows only the materialized next occurrence. An agent can distinguish this from list_posts, get_recurring_post and list_recurring_post without opening 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?

Gives the when-to-use boundary against list_posts ("Only the next occurrence of an ACTIVE series exists as a SCHEDULED post... list_posts shows it with recurringPostId set") and an explicit when-not / out-of-scope note that editing or skipping a date is only possible in the AdaptlyPost app. Paging guidance ("Page with offset while hasMore is true") and status filtering round out the invocation guidance.

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