AutomateSocials

Save a draft

save_draft

Saves a post you have written so it appears under Drafts and can be published or scheduled later. Use it whenever you write a post the user has not asked you to publish yet, instead of leaving it in the conversation: a draft in the chat is lost, a saved one is not. Always name the platforms it is for, and attach any picture you made for it. To change something that already exists, use edit_post rather than saving a second copy. Nothing is published by this.

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": {
      "text": "<text>",
      "platforms": "<platforms>"
    },
    "name": "save_draft"
  }
}

Input Schema

Name	Required	Description
`text`	Yes	The post body.
`title`	No	Internal title, never published.
`postId`	No	Revise this draft instead of saving a new one.
`thread`	No	Continuations for X or Threads.
`mediaIds`	No	Media ids, e.g. from generate_image.
`variants`	No	Per-platform wording, keyed by platform.
`platforms`	Yes	Which platforms this draft is for, e.g. ["x", "linkedin"]. Required: a draft that does not say where it is going cannot be shown beside the account it belongs to, and nobody can tell what it was written for.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true; the description adds the key consequence an agent actually needs, 'Nothing is published by this', and warns against creating duplicate copies, which speaks to idempotentHint=false. It does not cover revision behavior when postId is supplied beyond the schema's own note, so not a full 5.

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?

Five short sentences, front-loaded with the action and outcome, then when-to-use, then two corrective constraints. Every sentence carries distinct information with no repetition of the title or schema.

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?

Covers the decision an agent must make (save vs. chat vs. edit_post) and the publishing side effect, which is the main risk for a write tool with no output schema. Thread and variant handling are only in the schema, and the relationship to create_post/scheduling is not spelled out.

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 baseline is 3, but the description adds actionable emphasis the schema does not: platforms are mandatory in practice ('Always name the platforms it is for') and generated images must be attached. Nested thread/variants semantics are left to the schema alone.

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 plus the visible outcome: it saves a written post so it appears under Drafts and can be published or scheduled later. Distinguishes itself from edit_post and from leaving text in the conversation, so an agent can place it among the many post-related siblings.

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 an explicit trigger ('whenever you write a post the user has not asked you to publish yet'), an explicit anti-pattern (leaving it in chat, 'a draft in the chat is lost'), and an explicit alternative for the adjacent case ('To change something that already exists, use edit_post rather than saving a second copy').

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

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