Skip to main content
Glama
adaptlypost

AdaptlyPost

Official
by adaptlypost
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

List Posts

list_posts
Read-only

Find post IDs and review queued content by filtering status, platform, or date range. Returns posts newest first with per-platform status to audit what is scheduled or completed.

Instructions

List posts in the token's workspace, 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

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax results, 1 to 100
offsetNoPosts to skip; increase by limit while hasMore is true
endDateNoUpper bound (ISO 8601, e.g. "2026-03-31") on scheduledAt, or createdAt for posts never scheduled
statusesNoFilter by status (e.g. ["SCHEDULED", "DRAFT"]); omit for all statuses
platformsNoFilter to posts targeting any of these platforms
sortOrderNoNEWEST (default) or OLDEST
startDateNoLower bound (ISO 8601, e.g. "2026-03-01") on scheduledAt, or createdAt for posts never scheduled

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultNoAn object with posts (each with id, status, contentType, text, scheduledAt, timezone, and platforms with per-platform status), total (count of all matches), and hasMore.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed8 schema fields changedv0.1.1
    • 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."
  2. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the readOnlyHint and destructiveHint annotations, the description discloses the exact return shape ({ posts, total, hasMore }), the per-post status/platforms arrays, default sorting, filter behavior, and the special scheduledAt-vs-createdAt date semantics. This gives the agent a clear model of what the call does without contradicting the annotations.

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?

The description is four sentences and every sentence earns its place. The core result and scope are front-loaded, then filters and pagination, then the sibling routing. It is dense but not bloated given the tool's seven parameters.

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?

With seven optional parameters and multiple sibling tools, this description covers the response contract, pagination mechanics, filter semantics, and when to choose sibling tools. Nothing an agent needs to select and invoke this tool 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?

The schema already covers all parameters with 100% description coverage, so the baseline is 3. The description adds real value by explaining the interplay between startDate/endDate and scheduledAt versus createdAt, the 'any of these platforms' semantics for platforms, and pagination via offset while hasMore is true.

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 ('list posts in the token's workspace'), defines the scope (any status, newest first by default), and briefly describes the response shape. It also distinguishes itself from siblings by explicitly naming get_post and list_post_results in the final sentence.

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?

The description gives clear use cases: 'find post ids or check what is already queued.' It also names alternatives and their purposes, telling the agent when to use get_post for a full record and 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.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/adaptlypost/agent'

If you have feedback or need assistance with the MCP directory API, please join our Discord server