PostRite

List posts

list_posts

Read-only

List the organization's posts, newest scheduled time first unless sortBy/sortOrder say otherwise. Use this to find a post's ID before getting, updating, rescheduling, cancelling, or retrying it. Filter by status or a scheduled-time window. Returns compact post summaries (draft posts have scheduledAt: null and sort last in either direction; use get_post for full detail).

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

Name	Required	Description
`page`	No	Page number, 1-based (default 1)
`limit`	No	Page size (max 100, default 20)
`sortBy`	No	Column to order by, across every page (default scheduledAt). publishedAt puts unpublished posts last.
`status`	No	Only return posts in this status
`sortOrder`	No	desc (default here) = newest first; asc = oldest first, e.g. the next scheduled post with status SCHEDULED
`organizationId`	No	Organization to act in — an id from list_organizations. Required when this connection was authorized for more than one organization; omit it when there is only one.
`scheduledAfter`	No	ISO-8601 lower bound on scheduledAt
`scheduledBefore`	No	ISO-8601 upper bound on scheduledAt

Output Schema

Name	Required	Description	Default
`page`	No
`limit`	No
`posts`	No
`total`	No
`totalPages`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 5, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered; the description adds genuinely new behavioral context: default sort direction, the fact that draft posts have scheduledAt null and sort last in either direction, and that results are compact summaries rather than full records. It does not mention pagination limits or total-count behavior, which is the only notable gap.

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?

Four dense sentences, front-loaded with the operation and default ordering before moving to usage and return shape. Every sentence carries information an agent would otherwise have to infer, with no filler.

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?

Eight optional parameters, three enums, and an output schema are in play, and the description covers the decision-relevant pieces: default ordering, the organizationId scoping rule (echoed in the schema), the compact-vs-full distinction, and the edge case of unscheduled drafts. Since an output schema exists, it need not explain the return payload in detail.

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 description coverage is 100%, so page, limit, sortBy, sortOrder, status, organizationId and the scheduled bounds are all documented in the schema itself. The description only adds the "unless sortBy/sortOrder say otherwise" caveat and the scheduled-window filtering concept, which is marginal beyond what the schema provides — baseline 3 is appropriate.

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 — "List the organization's posts" — and immediately states the default ordering (newest scheduled time first). It explicitly contrasts itself with get_post ("compact post summaries ... use get_post for full detail"), so an agent can distinguish it from the sibling without opening a 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?

It names the exact downstream use case ("find a post's ID before getting, updating, rescheduling, cancelling, or retrying it") and the filtering modes available (status, scheduled-time window). That maps directly to the update_post, reschedule_post, cancel_post, and retry_post siblings, giving clear when-to-use routing.

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

All PostRite 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?