Skip to main content
Glama
FirstReply MCP Server

FirstReply MCP Server

Official
by FirstReply

Post List

post_list
Read-onlyIdempotent

Lists an organization's social media posts newest first or soonest upcoming, with filters for date, status, channel, and text; returns schedule, targets, publish state, and metrics.

Instructions

List the social media posts of an organization, newest first (order asc for upcoming posts, soonest first). Each post carries its text, status, scheduled time and its targets (one per channel) with their publish state and latest metrics.

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": {
      "organizationId": "<organizationId>"
    },
    "name": "post_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoOnly posts planned, published or created before this time. ISO 8601 date or date-time, e.g. 2026-09-01 or 2026-09-01T12:00:00Z.
fromNoOnly posts planned, published or created at or after this time. ISO 8601 date or date-time, e.g. 2026-09-01 or 2026-09-01T12:00:00Z.
pageNoPage number, starting at 1.
limitNoMaximum items to return (default 10, max 50).
orderNoasc lists the soonest first (calendar, upcoming posts); default desc.
searchNoText the post contains.
statusNoFilter by status, several comma-separated: DRAFT, PENDING_APPROVAL, SCHEDULED, PUBLISHING, PUBLISHED, PARTIALLY_FAILED, FAILED.
channelIdNoOnly posts to this channel.
organizationIdYesThe organization id. Use organization_list to find it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description adds useful context beyond them: default ordering (newest first), the ascending variant for upcoming posts, and the fact that each post expands to per-channel targets with publish state and latest metrics.

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?

Two tight sentences with the primary behavior and ordering front-loaded, followed by a single sentence describing the payload. Nothing is redundant or padded.

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 9-parameter list tool with no output schema, the description covers ordering defaults and summarizes the returned post structure (text, status, scheduled time, per-channel targets with publish state and metrics). Pagination defaults are left to the schema, which is acceptable given its full coverage.

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%, with the from/to/page/limit/order/status/channelId/search parameters fully documented in the schema. The description only reinforces the order semantics, adding little meaning the schema does not already carry, so baseline 3 is appropriate.

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 states a specific verb and resource ('List the social media posts of an organization') plus scope and return contents, so it is clearly distinguishable from post_get or post_metrics. It does not explicitly name a sibling or the boundary with post_analytics, which keeps it short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the resource scope and the parenthetical about using ascending order for upcoming posts. There is no explicit when-not guidance or routing to sibling list/analytics tools, so an agent must infer the boundaries.

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

Deploy Server

Other Tools