Skip to main content
Glama
Sign In
posterly-mcp-server

posterly-mcp-server

by awpthorp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

list_post_suggestions

Read-onlyIdempotent

Retrieve proactive, evidence-based weekly post suggestions in each account's learned voice, filterable by account and status, with pagination and full caption and rationale.

Instructions

List proactive post suggestions: evidence-based weekly drafts posterly writes in each account's learned voice, each with a rationale tying it back to what has performed well for that account. The caption, rationale, and account id are returned in full. Filter by account_id and status (pending, scheduled, dismissed; default pending). The output says whether every matching suggestion is shown; page with offset until it does. Read-only; requires a Pro plan or higher. Use dismiss_suggestion to hide one, or pass save_as_draft true on that tool to keep it as an unpublished draft.

Input Schema

NameRequiredDescriptionDefault
limitNoMax suggestions to return (default 20).
offsetNoHow many suggestions to skip. Use the offset the previous page gives to get the next page.
statusNoSuggestion status to list (default pending).
account_idNoFilter to one social account ID (from list_accounts).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.55.1

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations (read-only, non-destructive), the description provides critical behavioral constraints, such as requiring a 'Pro plan or higher,' which is a major operational constraint for an agent.

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?

While comprehensive, the description is slightly dense. However, every sentence contributes vital information regarding the suggestions' quality, operational constraints, or workflow integration, making it structurally sound.

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?

Given its complexity as an AI-driven, evidence-based workflow tool, the definition is exceptionally complete. It covers content quality, usage requirements, workflow integration, and result handling.

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?

Since schema coverage is 100%, the description primarily serves to elaborate on defaults (status 'pending') and define the high-level filtering goals of the parameters rather than defining their internal data structure.

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 is highly specific, defining the tool as a source for 'proactive post suggestions' that are evidence-based and written in an 'account's learned voice,' clearly distinguishing it from general post listing tools.

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?

The tool provides explicit usage guidance, detailing filtering options (account_id and status), how to handle large results (pagination via offset), and the required integration with other tools (using dismiss_suggestion).

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