PostOnce

create_workflow

Creates a future-content cross-post workflow from one source account to one or more target accounts. settings.content_filters limits which future posts are eligible.

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": {
      "name": "<name>",
      "source_account_id": "<source_account_id>",
      "target_account_ids": "<target_account_ids>"
    },
    "name": "create_workflow"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes
`settings`	No
`is_active`	No
`description`	No
`idempotency_key`	No
`source_account_id`	Yes
`target_account_ids`	Yes
`future_content_enabled`	No

Output Schema

Name	Required	Description
`body`	No	Upstream error details, when available.
`code`	No	Error code when the tool result has isError=true.
`data`	No	Present on successful results; omitted on tool errors.
`meta`	No
`status`	No
`message`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 3, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Beyond the annotations' write, non-destructive, and open-world signals, the description adds useful behavior: the workflow concerns future posts, supports one-to-many distribution, and can restrict eligibility through content filters. It leaves activation defaults, filter-combination behavior, destination publishing behavior, and idempotency unexplained.

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?

The core action and scope are front-loaded in one compact sentence, followed by one relevant configuration note. There is no redundant or low-value wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The output schema removes the need to describe return values, but this complex eight-parameter creation tool still lacks important invocation context. In particular, the opaque nested destination settings, undocumented flags and defaults, and unspecified filter semantics leave substantial gaps for non-basic calls.

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

Parameters2/5

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

With 0% schema description coverage, the two sentences provide only partial compensation by clarifying source/target roles and the general purpose of settings.content_filters. They do not explain the filter fields, destination_publish_settings, is_active, future_content_enabled, or idempotency_key.

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 uses a specific verb and resource, then narrows the scope to future-content cross-posting from one source to one or more targets. This clearly distinguishes the tool from siblings that create individual posts or drafts.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The future-content and cross-posting scope gives the agent a clear use case and implicitly excludes reposting existing content. It does not explicitly route users away from create_post, publish_post, or update_workflow for other scenarios.

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

All PostOnce 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?