Skip to main content
Glama
AdaptlyPost

AdaptlyPost

Official

Get Recurring Post

get_recurring_post
Read-onlyIdempotent

Retrieve one recurring post by id to inspect its status, pause reason, schedule, next occurrence, occurrence count, and per-platform content. Use it to verify or troubleshoot a recurring series.

Instructions

Get one recurring post (series) by id: status, pauseReason and lastError when paused, the schedule (frequency, interval, weekdays, startsAt, timezone, endsOn, maxOccurrences), nextOccurrenceAt (the next slot not yet created as a post; absent once ENDED), occurrenceCount (posts created so far), and the content and platforms each occurrence copies. Ids outside the workspace (the current one unless workspaceId names another) return "Recurring post not found". Ids come from list_recurring_posts, the recurringPostId returned by create_post, or the recurringPostId on a post from get_post or list_posts.

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

Input Schema

NameRequiredDescriptionDefault
idYesRecurring post ID from list_recurring_posts, create_post, or a post's recurringPostId
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 recurring post: id, userId, status, pauseReason, lastError, frequency, interval, weekdays, startsAt, timezone, endsOn, maxOccurrences, nextOccurrenceAt, occurrenceCount, contentType, text, mediaUrls, mediaAltTexts, thumbnailUrl, platformTypes, platforms, createdAt, and updatedAt.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.22.0

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the read-only annotations, the description discloses concrete behavior: pauseReason and lastError are populated when paused, nextOccurrenceAt is absent once ENDED, occurrenceCount reflects posts created so far, and ids outside the workspace return 'Recurring post not found.' These details meaningfully clarify return semantics and error conditions.

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?

The description is front-loaded with the core action and then supplies relevant field semantics and id provenance. It is dense but mostly purposeful; the long enumeration of return fields is somewhat redundant given the output schema, though the explanations for nextOccurrenceAt and paused fields add value.

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?

Given the moderate complexity and rich output schema, the description is complete enough to call the tool correctly. It covers id sourcing, workspace scoping, not-found behavior, field meanings, and absence conditions without unnecessary implementation detail.

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%, so the schema already documents both id and workspaceId thoroughly. The description repeats id sources and notes workspace scoping, but adds little semantic meaning beyond the schema's own parameter descriptions.

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 states a specific verb and resource: 'Get one recurring post (series) by id.' It then enumerates the returned details including status, schedule, nextOccurrenceAt, and occurrenceCount, making the tool's scope distinct from list_recurring_posts and get_post.

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?

It explains where valid ids come from: list_recurring_posts, create_post, or a post's recurringPostId from get_post/list_posts. It does not explicitly contrast when to use this versus listing recurring posts or fetching a normal post, but the 'one by id' framing provides clear usage context without exclusions.

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