Postly MCP

List Campaign Posts

postly_list_campaign_posts

Read-onlyIdempotent

Lists posts linked to a Postly campaign, newest first, with their status and targets. Use status published or failed to review outcomes. Requires campaigns.read and posts.read.

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": {
      "workspace_id": "<workspace_id>",
      "campaign_id": "<campaign_id>"
    },
    "name": "postly_list_campaign_posts"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Optional page size. Defaults to 20.
`before`	No	Optional post ID cursor. Pass the last post ID to load older posts.
`status`	No	Optional filter: all, published, failed, calendar, or a Postly post status. Defaults to all.
`campaign_id`	Yes	Postly campaign ID from postly_list_campaigns.
`workspace_id`	Yes	Postly workspace ID.

Output Schema

Name	Required	Description	Default
`code`	No
`data`	No
`message`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 2, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world, and non-destructive, so the safety profile is covered. The description adds genuinely new behavioral facts beyond them: sort order (newest first), the fields returned (status and targets), and the required scopes campaigns.read and posts.read.

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 short sentences with no waste: purpose and ordering first, then the practical status usage, then the auth requirement. Everything is front-loaded and each sentence carries distinct information.

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?

An output schema exists, so return values need no explanation, and pagination is covered by the schema's cursor and limit fields. Auth scopes are stated. Only a note on default result size or the relationship to sibling list tools is missing, which is minor.

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%, with limit, before, status, campaign_id, and workspace_id all documented in the schema, so the baseline is 3. The description only restates the status filter usage and adds no syntax or format detail beyond what the schema provides.

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?

States a specific verb and resource ('Lists posts linked to a Postly campaign') plus scope details (newest first, includes status and targets). This clearly separates it from postly_list_posts and postly_list_scheduled_posts by the campaign scoping, though it never names those siblings explicitly.

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?

'Use status published or failed to review outcomes' gives one concrete usage scenario, which is more than nothing. However, it offers no guidance on when to choose this over postly_list_posts, postly_get_campaign_report, or postly_get_post, and no exclusions.

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

All Postly MCP 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?