Skip to main content
Glama

List posts

list_posts

List posts of the API key's workspace (JSON with items, total, limit, offset; each item carries targets[] with channel, accountId, status and, for a failed target, failureReason and failureReasonCode, and needsReschedule on the post and each target, so the same caption on several networks is one post per network, not a duplicate; a WORDPRESS target carries its article summary but not the body: use get_post for contentHtml), optionally filtered by status (draft, scheduled, paused, publishing, published, failed, missed_slot: scheduled posts approved after their time, or still unapproved past it, that will not auto-publish until the user picks a new time; plain scheduled excludes them), channel, brandId and a scheduledAt range (from/to).

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_posts"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoscheduledAt upper bound, ISO 8601 with zone.
fromNoscheduledAt lower bound, ISO 8601 with zone.
limitNoPage size, 1-100.
offsetNoNumber of posts to skip.
statusNoOnly posts with this status, e.g. FAILED, PAUSED or MISSED_SLOT (case-insensitive).
brandIdNoOnly posts touching this brand.
channelNoOnly posts that have a target on this channel (UPPERCASE canonical, lowercase accepted).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full burden and does so unusually well: it describes the response envelope (items, total, limit, offset), the targets[] shape including failureReason/failureReasonCode, needsReschedule on both post and target, and the important non-obvious behavior that one caption on several networks is one post per network rather than a duplicate. It also discloses that WORDPRESS targets omit the body, which prevents a likely misinterpretation of the results.

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 core purpose is front-loaded in the first clause and every sentence earns its place by conveying non-obvious semantics. The main weakness is packaging: one long sentence with deeply nested parentheticals makes it harder to scan than a short bulleted structure would be.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 7-parameter list tool with no annotations and no output schema, the description is nearly complete: it covers the return envelope, per-target fields, dedup semantics, and status edge cases. The remaining gap is what an unfiltered call returns (all statuses including drafts?) and the default sort order, which an agent may need to paginate reliably.

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 would be 3, but the description adds real meaning beyond the schema by explaining MISSED_SLOT (approved after its time or still unapproved past it, will not auto-publish until the user picks a new time) and clarifying that plain 'scheduled' excludes those. The from/to semantics are only restated, not enriched.

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 opens with a specific verb and resource plus scope: 'List posts of the API key's workspace'. It explicitly names the sibling it is not ('use get_post for contentHtml'), so an agent can distinguish the two without opening either schema.

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 filter conditions (status, channel, brandId, scheduledAt range) and routes content retrieval to get_post, which is genuine when-to-use guidance. It stops short of stating exclusions against other list siblings (e.g. list_pending_approvals) or what a no-filter call returns, so it is clear but not fully disambiguating.

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