Skip to main content
Glama
atmosphere-ai

AdvisorPPC X Organic

by atmosphere-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Create thread

x_organic_create_thread

Publish a multi-post thread on X by sending the first post and chaining each following post as a reply, using only the copy you provide. Requires one-time confirmation and stops if a later post fails.

Instructions

Composite: publish the first post, then chain the rest as replies (in_reply_to of the previous). Use only the array of copy the user supplied — never invent posts. Requires confirm=true once for the whole thread. If a later post fails, STOP and return what already went up. X API pay-per-use (as of 2026): ~$0.015 per plain post, ~$0.20 per post that contains a link. Warn the user before posting links. X API has no native schedule. Use AdvisorPPC x_organic_schedule_* tools — never invent a publish time outside the job store.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
postsYes
confirmNoMust be true after the user explicitly named this action. Never set on your own.
reply_settingsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

With only readOnlyHint=false and openWorldHint=true, the description carries the behavioral burden and does so thoroughly: it discloses the composite publishing sequence, failure semantics (STOP and return), cost per post, link warning requirement, and lack of native scheduling. No contradiction with annotations.

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?

Dense and front-loaded: the composite definition comes first, followed by operationally critical rules. Every sentence contributes unique guidance (confirmation, failure, cost, scheduling) with no filler.

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?

Given the complexity, the description covers invocation, confirmation, failure, cost, and scheduling, and even indicates what to return on partial failure. It would be complete if it also addressed reply_settings and media handling, but those are partially inferable from the schema.

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 only 33%, but the description adds substantive semantics for posts (the array represents thread copy, first post then replies, never invent content) and confirm (once per whole thread). Reply_settings is not addressed in the description, leaving one parameter gap.

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 first sentence defines the operation as a composite: publish the first post and chain the remainder as replies, which is specific and distinct from x_organic_create_post or x_organic_reply. It names the resource (thread) and the exact behavior.

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 description gives explicit usage constraints: use only user-supplied copy, never invent posts, require confirm=true once, and stop on failure. It also routes scheduling to AdvisorPPC x_organic_schedule_* tools, making the alternative explicit.

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