Skip to main content
Glama

Publish Draft Post

autoposter_publish_draft
Destructive

Approves and immediately publishes an existing draft or pending post. Requires an API key with direct publish permission.

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": {
      "postId": "<postId>"
    },
    "name": "autoposter_publish_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
postIdYesThe post ID returned by autoposter_draft_post.

Output Schema

NameRequiredDescriptionDefault
statusYesTarget status ('queued' or 'scheduled').
messageNoStatus message or confirmation.
successYesWhether the draft was approved and queued/published.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "message": {
      +      "description": "Status message or confirmation.",
      +      "type": "string"
      +    },
      +    "status": {
      +      "description": "Target status ('queued' or 'scheduled').",
      +      "type": "string"
      +    },
      +    "success": {
      +      "description": "Whether the draft was approved and queued/published.",
      +      "type": "boolean"
      +    }
      +  },
      +  "required": [
      +    "success",
      +    "status"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, and the description reinforces the mutation by saying it publishes immediately. The genuinely additive piece is the auth requirement (an API key with direct publish permission), which an agent needs before calling. It stops short of saying whether the action can be reverted or what state results on partial failure.

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?

Two short sentences with the action front-loaded and the permission prerequisite second; no filler, no restating of the tool title.

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?

With one required parameter fully documented and an output schema covering return values, the description supplies the remaining essentials: what object it acts on, that the effect is immediate, and that elevated permissions are needed. Only post-publish state and failure behavior are unaddressed, which is minor for this complexity.

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

Parameters3/5

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

Schema coverage is 100% and the schema itself explains that postId comes from autoposter_draft_post. The description adds only that the target may be a draft or pending post, which is marginal beyond the schema. Baseline 3 is appropriate when the schema carries the parameter documentation.

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

Purpose4/5

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

The description pairs a specific verb ("approves and immediately publishes") with a specific resource ("an existing draft or pending post"), and the word "immediately" implicitly separates it from a scheduling sibling. It does not name an alternative sibling explicitly, so an agent must infer the boundary with autoposter_schedule_post.

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

Usage Guidelines3/5

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

Usage is implied through the precondition that the post must already exist as a draft or pending item, and the API-key requirement is stated as a gate. However, there is no explicit when-to-use-this-instead-of guidance against autoposter_schedule_post or autoposter_draft_post, leaving the choice to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources