Flaghand

Move, reorder, insert or edit a scheduled post on any workspace account without a passkey

updateScheduledPost

Destructive

Move, reorder, insert or edit a scheduled post on any workspace account without a passkey

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": {
      "id": "<id>",
      "rev": "<rev>"
    },
    "name": "updateScheduledPost"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	Scheduled job ID or stable workspace post number, such as "#38" or "38".
`rev`	Yes	Current draft revision from getDraft. A concurrent edit or move is refused.
`body`	No	The exact platform body: x_post or linkedin_post {text, media?: [{media_id, alt}]}; x_thread {posts: [{text, media?}, …]}. The full schema also includes LinkedIn documents, cards, TikTok and slideshows. The API validates the complete body.
`mode`	No
`title`	No
`post_at`	No	Exact future posting time, with UTC offset. At least one minute ahead. Never now.
`workspace`	No	Leave out for the token's workspace (ws_…).
`connection_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 7, 2026

TDQS

C2/5.0

Behavior2/5

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

The annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is known. The description adds little beyond repeating the annotation title: it does not explain the required revision model, concurrent-edit refusal, side effects of moving/reordering, or authentication implications of 'without a passkey.'

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence with no wasted wording, but it is under-specified rather than appropriately concise for an 8-parameter destructive mutation. It merely restates the tool title and front-loads no operational constraints.

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?

For a complex destructive mutation with nested body parameters, no output schema, and concurrency controls, the description is far from complete. It lacks prerequisites, revision-workflow context, sibling differentiation, and return or error behavior, giving the agent only a broad purpose statement.

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 8 parameters and only 63% schema description coverage, the description contributes no parameter meaning at all. It does not document undocumented fields such as mode, title, or connection_id, nor clarify the required id/rev relationship or nested body structure.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tautological: description restates name/title.

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

Usage Guidelines2/5

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

No guidance is given on when to use this tool versus schedulePost, unschedulePost, updateDraft, or the draft tools. The only scoping phrases are 'any workspace account' and 'without a passkey,' neither of which explains selection criteria or exclusions.

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

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