Skip to main content
Glama
Socifyr MCP

Socifyr MCP

by Socifyr

update_post

Edit a draft or scheduled post to change its text, media, schedule, or target accounts. Pass the complete desired account set when replacing connections.

Instructions

Edit an existing draft or scheduled post — change its text, media, schedule, or which accounts it posts to. Only drafts and not-yet-published scheduled posts can be edited. IMPORTANT: "connections" is a FULL REPLACEMENT of the target accounts, not a delta — to add or remove one account, pass the complete desired set of slugs (use list_posts / list_connections first to see the current ones).

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": "update_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNoNew caption/body text
titleNoNew title
postIdYesThe draft or scheduled post ID (from list_posts)
mediaIdsNoMedia library IDs to attach (replaces current media)
connectionsNoFULL set of connection slugs the post should go to (replaces the current set)
descriptionNoNew description
scheduledAtNoNew ISO 8601 schedule time. For a scheduled post this must be in the future.
firstCommentNoFirst comment text (e.g. hashtags)
contentFormatNoContent format override

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does disclose a meaningful side effect: connections is a full replacement, not a delta, so a partial list silently drops accounts. It also discloses the editability restriction. It stops short of describing return values or what happens to fields left unspecified.

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?

Three sentences, front-loaded with purpose, then the eligibility constraint, then the highest-risk caveat flagged with IMPORTANT. The restatement in the replacement warning is deliberate emphasis on a destructive default, not filler.

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 nine-parameter mutation tool with no annotations and no output schema, it covers the two things most likely to cause damage: which posts are editable and how connections are replaced. It does not state whether omitted fields are preserved or cleared, which matters for an update tool with several replace-style fields.

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 every parameter is already documented, and the schema itself says connections and mediaIds replace current values. The description reinforces the replacement danger for connections but adds no new semantics for the other eight parameters. 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 opens with a specific verb and resource ("Edit an existing draft or scheduled post") and enumerates the mutable aspects (text, media, schedule, target accounts). That scope naturally separates it from sibling mutators like publish_draft or schedule_post, which create or advance a post rather than mutate it.

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 states an explicit eligibility rule: only drafts and not-yet-published scheduled posts can be edited, which is a real when-not constraint. It also names list_posts and list_connections as prerequisites for gathering current state, though it doesn't explicitly route the agent elsewhere for publishing or rescheduling workflows.

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