Skip to main content
Glama
Sign In
social0-mcp

social0-mcp

by Abhishek-B-R
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

update_post

Edit a scheduled or draft post by modifying its caption, platforms, or media to adjust content before publishing.

Instructions

Update an existing Social0 draft or scheduled post — change caption, platforms, or media. Use when the user wants to edit a post before publishing.

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_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
mediaNoUpdated media IDs
contentNoUpdated caption
post_idYesPost 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 observedv0.3.0

TDQS

A3.6/5.0
Behavior2/5

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

No annotations provided, so description bears full burden. It identifies this as a mutation and lists updatable fields, but doesn't disclose idempotency, required permissions, validation behavior, or side effects (e.g., does updating a scheduled post affect scheduling?). Missing critical behavioral traits for a write 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 sentences, no filler. Front-loaded with purpose, immediately usable by an agent. Every word adds value.

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?

Despite 5 parameters (including a complex nested object) and no output schema, the description is minimal. It omits the advanced platform_options details, return value expectations, and edge cases (e.g., what happens if post is already published). Leaves the agent underinformed for correct invocation.

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% with descriptions for all 5 parameters. The description restates three parameters (caption, platforms, media) but adds no new detail, especially for the complex 'platform_options' parameter. Does not compensate beyond the schema, so baseline 3 is 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 explicitly states the action 'Update' and the resource 'existing Social0 draft or scheduled post', with specific modifiable elements (caption, platforms, media). It distinguishes from siblings like publish_post by clarifying it applies to pre-publishing edits.

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?

Clearly states 'Use when the user wants to edit a post before publishing', providing direct usage context. Lacks explicit when-not-to-use or alternative recommendations, but the sibling set makes the scope reasonably clear.

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

Deploy Server

Other Tools