Skip to main content
Glama

List posts

list_posts
Read-onlyIdempotent

Posts in a workspace, newest first, with cursor pagination: pass next_cursor as cursor. Filters combine: status, network, channel_id (one account), group_id (posts to any account in that group), query (words in the caption or internal label), and from/to on the scheduled time. Date-only from/to filters use inclusive UTC days, not workspace-local days. Offset timestamps filter exact instants. Posts without a date (unscheduled drafts) only appear without from/to.

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": {
      "workspace_id": "<workspace_id>"
    },
    "name": "list_posts"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoOnly posts scheduled at or before this date (inclusive) or instant.
fromNoOnly posts scheduled at or after this date (2026-10-01) or instant.
limitNo
queryNoWords to find in the caption or the internal label (case-insensitive).
cursorNonext_cursor from the previous page.
statusNo
networkNoOnly posts going to at least one account on this network.
group_idNoOnly posts going to at least one account in this group (from list_groups).
channel_idNoOnly posts going to this account (from list_channels).
workspace_idYesWorkspace id from list_workspaces

Output Schema

NameRequiredDescriptionDefault
itemsYes
next_cursorYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / network / enum
      Previous value: -[
      -  "FACEBOOK",
      -  "INSTAGRAM",
      -  "LINKEDIN",
      -  "TIKTOK",
      -  "YOUTUBE",
      -  "X",
      -  "BLUESKY",
      -  "TELEGRAM",
      -  "MASTODON",
      -  "THREADS",
      -  "PINTEREST",
      -  "TUMBLR",
      -  "GOOGLE_BUSINESS",
      -  "WHATSAPP"
      -]New value: +[
      +  "FACEBOOK",
      +  "INSTAGRAM",
      +  "LINKEDIN",
      +  "TIKTOK",
      +  "YOUTUBE",
      +  "X",
      +  "BLUESKY",
      +  "TELEGRAM",
      +  "MASTODON",
      +  "THREADS",
      +  "PINTEREST",
      +  "GOOGLE_BUSINESS",
      +  "PIXELFED",
      +  "TUMBLR",
      +  "NOSTR",
      +  "PEERTUBE",
      +  "REDDIT",
      +  "SNAPCHAT",
      +  "WHATSAPP"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / network / enum
      Previous value: -[
      -  "FACEBOOK",
      -  "INSTAGRAM",
      -  "LINKEDIN",
      -  "TIKTOK",
      -  "YOUTUBE",
      -  "X",
      -  "BLUESKY",
      -  "TELEGRAM",
      -  "MASTODON",
      -  "THREADS",
      -  "PINTEREST",
      -  "GOOGLE_BUSINESS",
      -  "WHATSAPP"
      -]New value: +[
      +  "FACEBOOK",
      +  "INSTAGRAM",
      +  "LINKEDIN",
      +  "TIKTOK",
      +  "YOUTUBE",
      +  "X",
      +  "BLUESKY",
      +  "TELEGRAM",
      +  "MASTODON",
      +  "THREADS",
      +  "PINTEREST",
      +  "TUMBLR",
      +  "GOOGLE_BUSINESS",
      +  "WHATSAPP"
      +]
  3. Changed1 schema field changed
    • changedInput schema / properties / network / enum
      Previous value: -[
      -  "FACEBOOK",
      -  "INSTAGRAM",
      -  "LINKEDIN",
      -  "TIKTOK",
      -  "YOUTUBE",
      -  "X",
      -  "BLUESKY",
      -  "TELEGRAM",
      -  "MASTODON",
      -  "THREADS",
      -  "PINTEREST",
      -  "WHATSAPP"
      -]New value: +[
      +  "FACEBOOK",
      +  "INSTAGRAM",
      +  "LINKEDIN",
      +  "TIKTOK",
      +  "YOUTUBE",
      +  "X",
      +  "BLUESKY",
      +  "TELEGRAM",
      +  "MASTODON",
      +  "THREADS",
      +  "PINTEREST",
      +  "GOOGLE_BUSINESS",
      +  "WHATSAPP"
      +]
  4. Changed1 schema field changed
    • changedInput schema / properties / network / enum
      Previous value: -[
      -  "FACEBOOK",
      -  "INSTAGRAM",
      -  "LINKEDIN",
      -  "TIKTOK",
      -  "YOUTUBE",
      -  "X",
      -  "BLUESKY",
      -  "TELEGRAM",
      -  "MASTODON",
      -  "THREADS",
      -  "WHATSAPP"
      -]New value: +[
      +  "FACEBOOK",
      +  "INSTAGRAM",
      +  "LINKEDIN",
      +  "TIKTOK",
      +  "YOUTUBE",
      +  "X",
      +  "BLUESKY",
      +  "TELEGRAM",
      +  "MASTODON",
      +  "THREADS",
      +  "PINTEREST",
      +  "WHATSAPP"
      +]
  5. Changed1 schema field changed
    • changedInput schema / properties / network / enum
      Previous value: -[
      -  "FACEBOOK",
      -  "INSTAGRAM",
      -  "LINKEDIN",
      -  "TIKTOK",
      -  "YOUTUBE",
      -  "X",
      -  "BLUESKY",
      -  "TELEGRAM",
      -  "WHATSAPP"
      -]New value: +[
      +  "FACEBOOK",
      +  "INSTAGRAM",
      +  "LINKEDIN",
      +  "TIKTOK",
      +  "YOUTUBE",
      +  "X",
      +  "BLUESKY",
      +  "TELEGRAM",
      +  "MASTODON",
      +  "THREADS",
      +  "WHATSAPP"
      +]
  6. Changed1 schema field changed
    • changedInput schema / properties / network / enum
      Previous value: -[
      -  "FACEBOOK",
      -  "INSTAGRAM",
      -  "LINKEDIN",
      -  "TIKTOK",
      -  "YOUTUBE",
      -  "X",
      -  "BLUESKY",
      -  "WHATSAPP"
      -]New value: +[
      +  "FACEBOOK",
      +  "INSTAGRAM",
      +  "LINKEDIN",
      +  "TIKTOK",
      +  "YOUTUBE",
      +  "X",
      +  "BLUESKY",
      +  "TELEGRAM",
      +  "WHATSAPP"
      +]
  7. Changed1 schema field changed
    • changedInput schema / properties / network / enum
      Previous value: -[
      -  "FACEBOOK",
      -  "INSTAGRAM",
      -  "LINKEDIN",
      -  "TIKTOK",
      -  "YOUTUBE",
      -  "X",
      -  "WHATSAPP"
      -]New value: +[
      +  "FACEBOOK",
      +  "INSTAGRAM",
      +  "LINKEDIN",
      +  "TIKTOK",
      +  "YOUTUBE",
      +  "X",
      +  "BLUESKY",
      +  "WHATSAPP"
      +]
  8. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description still adds real behavior: result ordering, the cursor loop protocol, the workspace-local vs UTC day distinction, and the exclusion of undated posts under date filters. Return shape is covered by the output schema, so nothing critical is missing.

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?

Three sentences, front-loaded with the resource and ordering, then pagination, then filter semantics. Dense but nearly every clause carries distinct information; the parenthetical gloss on query duplicates the schema slightly, which keeps it from a 5.

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 10-parameter filtered-list tool, the description covers ordering, pagination, filter combination, timezone semantics, and the undated-post edge case. With annotations covering safety and an output schema covering returns, an agent has everything it needs to call this correctly.

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 80%, so the baseline is 3, and the description earns above that by explaining AND-combination of filters, the group_id vs channel_id distinction (any account in group vs one account), and the date-only vs offset-timestamp semantics. The query and network explanations largely restate the schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource (posts), the scope (a workspace), the ordering (newest first), and the pagination model (cursor). That is more than a tautology of the name. It does not explicitly contrast with siblings such as list_comments or get_analytics, but for a list tool the purpose is unambiguous.

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 gives concrete usage rules: filters combine, cursor is fed by next_cursor, and date-only from/to operate on inclusive UTC days while offset timestamps match exact instants. It also states the when-not case implicitly — undated drafts only appear when from/to are omitted. It stops short of routing to sibling tools, so a 4 rather than 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources