AdaptlyPost

List Posts

list_posts

Read-only

List posts in the workspace (the current one unless workspaceId names another), any status, newest first by default. Returns { posts, total, hasMore }; each post carries its status and a platforms array with per-platform status. Filters: statuses, platforms (posts targeting any of them), and startDate/endDate, which bound scheduledAt, or createdAt for posts never scheduled. limit is 1 to 100 (default 20); page with offset while hasMore is true. Use this to find post ids or check what is already queued. Use get_post for one post's full record and list_post_results for one post's per-platform outcomes and retry ids.

Input Schema

Name	Required	Description
`limit`	No	Max results, 1 to 100
`offset`	No	Posts to skip; increase by limit while hasMore is true
`endDate`	No	Upper bound (ISO 8601, e.g. "2026-03-31") on scheduledAt, or createdAt for posts never scheduled
`statuses`	No	Filter by status (e.g. ["SCHEDULED", "DRAFT"]); omit for all statuses
`platforms`	No	Filter to posts targeting any of these platforms
`sortOrder`	No	NEWEST (default) or OLDEST
`startDate`	No	Lower bound (ISO 8601, e.g. "2026-03-01") on scheduledAt, or createdAt for posts never scheduled
`workspaceId`	No	Workspace 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

Name	Required	Description	Default
`result`	No	An object with posts (each with id, status, contentType, text, scheduledAt, timezone, recurringPostId and occurrenceAt for occurrences of a recurring post, and platforms with per-platform status), total (count of all matches), and hasMore.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 27, 2026

changedInput schema / properties / platforms / description

Previous value: -"Filter to posts targeting any of these platforms. TELEGRAM matches posts created in the AdaptlyPost app"New value: +"Filter to posts targeting any of these platforms"

changedInput schema / properties / platforms / items / enum

Previous value: -[
-  "LINKEDIN",
-  "YOUTUBE",
-  "INSTAGRAM",
-  "FACEBOOK",
-  "TIKTOK",
-  "PINTEREST",
-  "THREADS",
-  "BLUESKY",
-  "TWITTER",
-  "MASTODON",
-  "GOOGLE_BUSINESS",
-  "TELEGRAM"
-]New value: +[
+  "LINKEDIN",
+  "YOUTUBE",
+  "INSTAGRAM",
+  "FACEBOOK",
+  "TIKTOK",
+  "PINTEREST",
+  "THREADS",
+  "BLUESKY",
+  "TWITTER",
+  "MASTODON",
+  "GOOGLE_BUSINESS",
+  "TUMBLR",
+  "TELEGRAM"
+]

Changed2 schema fields changedOct 13, 2026

changedInput schema / properties / platforms / description

Previous value: -"Filter to posts targeting any of these platforms"New value: +"Filter to posts targeting any of these platforms. TELEGRAM matches posts created in the AdaptlyPost app"

changedInput schema / properties / platforms / items / enum

Previous value: -[
-  "LINKEDIN",
-  "YOUTUBE",
-  "INSTAGRAM",
-  "FACEBOOK",
-  "TIKTOK",
-  "PINTEREST",
-  "THREADS",
-  "BLUESKY",
-  "TWITTER",
-  "MASTODON"
-]New value: +[
+  "LINKEDIN",
+  "YOUTUBE",
+  "INSTAGRAM",
+  "FACEBOOK",
+  "TIKTOK",
+  "PINTEREST",
+  "THREADS",
+  "BLUESKY",
+  "TWITTER",
+  "MASTODON",
+  "GOOGLE_BUSINESS",
+  "TELEGRAM"
+]

Changed2 schema fields changedSep 28, 2026

removedInput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

removedOutput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

Changed6 schema fields changedSep 27, 2026

addedInput schema / properties / limit / maximum
```
Added value: +100
```
addedInput schema / properties / limit / minimum
```
Added value: +1
```

changedInput schema / properties / limit / type

Previous value: -"number"New value: +"integer"

addedInput schema / properties / offset / minimum
```
Added value: +0
```

changedInput schema / properties / offset / type

Previous value: -"number"New value: +"integer"

changedInput schema / properties / workspaceId / description

Previous value: -"Workspace to act in: an id from list_workspaces. Omit to use the default workspace. Use the same workspaceId for every call about the same workspace, since ids from one workspace (accounts, posts, uploads) do not exist in another"New value: +"Workspace 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"

Changed1 schema field changedSep 27, 2026

addedInput schema / properties / workspaceId

Added value: +{
+  "description": "Workspace to act in: an id from list_workspaces. Omit to use the default workspace. Use the same workspaceId for every call about the same workspace, since ids from one workspace (accounts, posts, uploads) do not exist in another",
+  "type": "string"
+}

Changed1 schema field changedSep 26, 2026

changedOutput schema / properties / result / description

Previous value: -"An object with posts (each with id, status, contentType, text, scheduledAt, timezone, and platforms with per-platform status), total (count of all matches), and hasMore."New value: +"An object with posts (each with id, status, contentType, text, scheduledAt, timezone, recurringPostId and occurrenceAt for occurrences of a recurring post, and platforms with per-platform status), total (count of all matches), and hasMore."

Changed1 schema field changedSep 23, 2026

changedInput schema / properties / platforms / items / enum

Previous value: -[
-  "LINKEDIN",
-  "YOUTUBE",
-  "INSTAGRAM",
-  "FACEBOOK",
-  "TIKTOK",
-  "PINTEREST",
-  "THREADS",
-  "BLUESKY",
-  "TWITTER"
-]New value: +[
+  "LINKEDIN",
+  "YOUTUBE",
+  "INSTAGRAM",
+  "FACEBOOK",
+  "TIKTOK",
+  "PINTEREST",
+  "THREADS",
+  "BLUESKY",
+  "TWITTER",
+  "MASTODON"
+]

Changed8 schema fields changedSep 8, 2026

changedInput schema / properties / endDate / description

Previous value: -"End date (ISO 8601)"New value: +"Upper bound (ISO 8601, e.g. \"2026-03-31\") on scheduledAt, or createdAt for posts never scheduled"

changedInput schema / properties / limit / description

Previous value: -"Max results"New value: +"Max results, 1 to 100"

changedInput schema / properties / offset / description

Previous value: -"Pagination offset"New value: +"Posts to skip; increase by limit while hasMore is true"

changedInput schema / properties / platforms / description

Previous value: -"Filter by platform"New value: +"Filter to posts targeting any of these platforms"

changedInput schema / properties / sortOrder / description

Previous value: -"NEWEST or OLDEST"New value: +"NEWEST (default) or OLDEST"

changedInput schema / properties / startDate / description

Previous value: -"Start date (ISO 8601)"New value: +"Lower bound (ISO 8601, e.g. \"2026-03-01\") on scheduledAt, or createdAt for posts never scheduled"

changedInput schema / properties / statuses / description

Previous value: -"Filter by status (e.g. [\"SCHEDULED\", \"DRAFT\"])"New value: +"Filter by status (e.g. [\"SCHEDULED\", \"DRAFT\"]); omit for all statuses"

changedOutput schema / properties / result / description

Previous value: -"The matching posts with their ids, statuses, platforms, and schedule times as returned by the AdaptlyPost API."New value: +"An object with posts (each with id, status, contentType, text, scheduledAt, timezone, and platforms with per-platform status), total (count of all matches), and hasMore."

First observedSep 1, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already declare readOnly/openWorld=false/destructive=false, and the description adds substantive context beyond them: default newest-first ordering, the aggregate return shape { posts, total, hasMore }, that each post carries status plus a per-platform platforms array, and that startDate/endDate bound scheduledAt or createdAt for unscheduled posts. Pagination contract (offset while hasMore) is spelled out.

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 core action and scope, then return shape, then filters, then routing to siblings. No sentence is redundant despite covering a lot of ground.

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 an 8-parameter, zero-required listing tool with an output schema, the description covers scope, ordering, filtering semantics, pagination, and sibling routing. Nothing an agent needs in order to call it 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 still earns credit by explaining that platforms matches posts targeting ANY of the listed platforms and by restating the date-bound semantics and the 1-100/20 default. It adds meaning rather than merely echoing the schema, though most of the syntax detail already lives in the fields.

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?

States a specific verb+resource (list posts), defines scope (current workspace unless workspaceId names another), default ordering, and return shape. It also explicitly distinguishes itself from get_post and list_post_results, so an agent can choose 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?

Gives the positive use case ('find post ids or check what is already queued') and names the two alternatives with the conditions that select them: get_post for a full record, list_post_results for per-platform outcomes and retry ids.

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

All AdaptlyPost tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?