Galatic.ai

List planned posts

auto_publish_list_posts

Read-onlyIdempotent

List the posts of an Orion-mode Auto Publish campaign, newest first, up to 50. Returns { campaignId, counts (per status), batch, posts }, plus entitlement and slotCap when no batchId is given. Use it to follow a plan from auto_publish_plan_posts (pass its batchId; a batch past its planning deadline is marked failed here) or to find posts to review; use auto_publish_update_post to approve, skip or edit one. campaignId defaults to the user's active Orion-mode campaign.

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": {
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "auto_publish_list_posts"
  }
}

Input Schema

Name	Required	Description
`status`	No	Comma-separated: planned, generating, review, approved, published, failed, skipped.
`batchId`	No	batchId from auto_publish_plan_posts; also returns that batch's status.
`context`	Yes	Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution."
`llm_model`	Yes	The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" — never guess.
`campaignId`	No	Auto Publish campaign id. Defaults to the active Orion-mode campaign.
`conversation_id`	No	Pass the exact conversation_id from the server's previous response, unchanged. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it. Keep passing the same conversation_id for the rest of the conversation, including after later user messages or on a different task; do not reset it when the user starts a new request.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 26, 2026

addedInput schema / properties / batchId / description

Added value: +"batchId from auto_publish_plan_posts; also returns that batch's status."

addedInput schema / properties / campaignId / description

Added value: +"Auto Publish campaign id. Defaults to the active Orion-mode campaign."

addedInput schema / properties / status / description

Added value: +"Comma-separated: planned, generating, review, approved, published, failed, skipped."

First observedOct 24, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already cover read-only/idempotent/non-destructive, so the description correctly spends its words elsewhere: it discloses the response envelope, that entitlement and slotCap only appear without a batchId, that a batch past its planning deadline surfaces as failed, and that campaignId defaults to the active Orion campaign. The one omission is whether the 50-item cap is a silent truncation (no cursor parameter exists), which an agent would want to know.

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 sentences, zero filler: what it returns first, then when to use it, then the default. The brace-notation return summary is compact and carries information the agent cannot get elsewhere since there is no output schema.

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?

With no output schema, the description takes on the job of describing the return shape and does so, and all six parameters (including the two required plumbing params) are covered by rich schema descriptions. An agent has everything needed to call it correctly and interpret the result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so baseline is 3; the description still adds real meaning by explaining why batchId matters (it comes from auto_publish_plan_posts and triggers the deadline-failure signal) and by restating the campaignId default as a behavioral rule rather than a field note.

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 of an Orion-mode Auto Publish campaign) plus ordering and a hard cap (newest first, up to 50). It is immediately distinguishable from auto_publish_plan_posts and auto_publish_update_post, which it names.

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?

Gives two explicit use cases (following a plan by passing batchId, and finding posts to review) and names the sibling to use for the follow-up action (auto_publish_update_post to approve, skip or edit). When-to-use and the alternative path are both spelled out.

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

All Galatic.ai 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.