Skip to main content
Glama
Sign In

Galatic.ai

by ai.galatic
OverviewDiscussionsAdmin

Plan posts

auto_publish_plan_posts

Start planning a batch of social video posts for an Orion-mode Auto Publish campaign. Runs in the background: returns at once with { campaignId, batchId, status "planning", count, slotCap }; poll auto_publish_list_posts with that batchId until batch.status is "done" or "failed". Spends Galatic.AI credits (research searches plus planning, checked before it starts), uses the plan's monthly post slots, and needs a paid plan. Planned posts are not published: review them with auto_publish_update_post. campaignId defaults to the user's active Orion-mode campaign; template-mode campaigns are refused.

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_plan_posts"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNoPosts to plan, 1-10 (default 5); trimmed to the slots left this month.
focusNoOptional theme or angle for this batch.
contextYesExplain 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_modelYesThe 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.
campaignIdNoAuto Publish campaign id. Defaults to the active Orion-mode campaign.
conversation_idNoPass 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.

  1. Changed5 schema fields changed
    • addedInput schema / properties / campaignId / description
      Added value: +"Auto Publish campaign id. Defaults to the active Orion-mode campaign."
    • addedInput schema / properties / count / description
      Added value: +"Posts to plan, 1-10 (default 5); trimmed to the slots left this month."
    • changedInput schema / properties / count / maximum
      Previous value: -9007199254740991New value: +10
    • changedInput schema / properties / count / minimum
      Previous value: --9007199254740991New value: +1
    • addedInput schema / properties / focus / description
      Added value: +"Optional theme or angle for this batch."
  2. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses background/async execution, the exact immediate return payload ({campaignId, batchId, status, count, slotCap}), the polling contract, credit spend with a pre-check, monthly slot consumption, and the paid-plan prerequisite. Annotations only say non-readonly, non-destructive, non-idempotent, closed-world, so this description carries real added behavioral weight.

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?

Front-loads what the tool does and that it runs in the background, then packs return shape, polling instruction, cost/slot side effects, and the non-publishing caveat into tight clauses 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?

No output schema exists, yet the description supplies the immediate return shape, the async completion path, and the side-effect envelope (credits, slots, plan requirement). Nothing an agent needs in order to call it and handle the result is missing.

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 coverage is 100%, so the schema already documents count, focus, context, llm_model, campaignId, and conversation_id. The description adds one meaningful constraint beyond schema text: campaignId defaults to the active Orion-mode campaign and template-mode campaigns are refused. Other params are left to the schema.

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 ('start planning'), resource ('a batch of social video posts'), and scope ('Orion-mode Auto Publish campaign'). It is immediately distinguishable from siblings auto_publish_list_posts (polling), auto_publish_update_post (reviewing), and publish_post_now (publishing).

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?

Explicitly names the follow-up action and the alternative tool: poll auto_publish_list_posts with the returned batchId until status is 'done' or 'failed'. It also states an exclusion (template-mode campaigns are refused) and directs review to auto_publish_update_post rather than publishing.

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

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