Skip to main content
Glama

Social0

update_draft

Update an unpublished Social0 draft or scheduled post — caption, platforms, or media. Does not edit already-published live posts. Use before publish_post / schedule_post.

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": {
      "post_id": "<post_id>"
    },
    "name": "update_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
mediaNoUpdated media IDs
contentNoUpdated caption
post_idYesDraft or scheduled post ID to update
platformsNoUpdated target platforms or account IDs
platform_optionsNoAdvanced per-platform settings. Supports content/caption and media per platform, plus pinterest board_id/title/link/create_board, tiktok title/privacy/draft/comment/duet/stitch/commercial/AI flags, instagram cover_image_url/trial_reel, youtube title, and x/twitter_x madeWithAi/paidPartnership.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare this is a non-readonly, non-destructive, non-idempotent mutation. The description adds the important scope constraint that live published posts cannot be edited, which goes beyond annotations. However, it does not explain whether omitted fields are preserved or replaced, how media/platform arrays are merged, or any permission requirements, which are relevant for an update operation.

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 compact sentences front-load the action and scope, then add the exclusion and workflow context. There is no filler or repeated schema information.

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?

For a five-parameter mutation with a nested platform_options object, the description covers the core scope, exclusions, and workflow placement, while the rich schema handles field-level detail. The remaining gap is partial-update semantics, which would help an agent know whether omitted fields are left unchanged.

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 description coverage is 100%, so the input schema already documents post_id, content, platforms, media, and the nested platform_options. The description only restates the editable categories and adds no syntax, format, or interaction details beyond the schema, making the baseline 3 appropriate.

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 states a specific verb and resource ('Update an unpublished Social0 draft or scheduled post') and immediately scopes it by the editable fields ('caption, platforms, or media'). It also distinguishes the tool from live-post editing and names downstream siblings, so an agent can separate it from publish_post and schedule_post without opening the schema.

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?

It gives clear usage context: call this before publish_post or schedule_post, and do not use it for already-published posts. The main gap is that it does not mention create_draft or delete_draft as alternatives for new or removed drafts, but the primary when/when-not guidance is explicit.

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.