Skip to main content
Glama

list_posts

Read-only

List posts in the workspace. Filter by status to see drafts, scheduled, published, or failed posts. Returns a formatted table with content preview, channels, dates, and post IDs. The content cell shows the default caption; if a post has per-platform overrides (e.g. a custom X version) the preview is suffixed with (per-platform) — call get_post to see every variant.

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
tagNoOnly posts with this tag: a tag name or id; comma separate several for any of them. See list_tags.
limitNoMax results (default: 20)
offsetNoOffset for pagination
statusNoFilter by status: draft, scheduled, published, failed

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / tag
      Added value: +{
      +  "description": "Only posts with this tag: a tag name or id; comma separate several for any of them. See list_tags.",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare this a read-only, non-destructive, closed-world operation, so the safety profile is covered. The description adds genuine value beyond that by describing the return shape (formatted table with content preview, channels, dates, post IDs) and a non-obvious display rule: previews are suffixed with *(per-platform)* when caption overrides exist. It does not cover pagination behavior or empty-result handling, which keeps it below a 5.

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?

Three sentences, front-loaded with the core operation, then filtering, then return semantics. Every sentence earns its place, including the cross-reference to `get_post`, which prevents a likely misuse.

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?

With no output schema, the description carries the burden of explaining returns, and it does so adequately for a simple read tool. The only meaningful gap is pagination/limit behavior, which is left entirely to the schema's terse descriptions.

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 coverage is 100%, so `tag`, `limit`, `offset`, and `status` are already documented in the input schema. The description only reinforces the status values, which the schema already lists, and says nothing about tag semantics or pagination defaults. Baseline 3 is appropriate when the schema carries the parameter burden.

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 and resource ('List posts in the workspace') and immediately scopes it with the available status filter. It also names the sibling it is not ('call `get_post` to see every variant'), so an agent can distinguish list-level from detail-level retrieval 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?

Gives a clear condition for the status filter (drafts, scheduled, published, failed) and explicitly routes the agent to `get_post` when per-platform variants matter. It stops short of contrasting against other listing tools such as `get_calendar` or `get_post_status`, so a small amount of inference remains.

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