Skip to main content
Glama

Soclo

by app.soclo
OverviewDiscussionsAdmin

Edit a saved post draft

soclo_posts_edit_draft
DestructiveIdempotent

Replace the caption and/or hashtags of one saved draft in Soclo with the supplied text. Pass its postId, current expectedRevision, draftPatch and a stable clientRequestId. Without confirm:true, previews and changes nothing; with confirm:true, saves only if it is still a draft at that revision and returns the receipt and current draft. Does not generate text, change media, schedule, publish or contact social accounts. Free; needs plan:create.

Input Schema

NameRequiredDescriptionDefault
postIdYesThe draft id, from soclo_posts_drafts.
confirmNotrue only after the owner approved this exact change. Omit or false for a preview that changes nothing.
draftPatchYes
clientRequestIdYes
expectedRevisionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / confirm / description
      Previous value: -"true only after the owner agreed to cancel that exact post. Omit or pass false to get a preview instead: nothing is cancelled and nothing else is fetched."New value: +"true only after the owner approved this exact change. Omit or false for a preview that changes nothing."
    • changedInput schema / properties / postId / description
      Previous value: -"The post id, from soclo_posts_list."New value: +"The draft id, from soclo_posts_drafts."
    • changedInput schema / required
      Previous value: -[
-  "postId",
-  "clientRequestId",
-  "expectedRevision",
-  "draftPatch"
-]New value: +[
+  "clientRequestId",
+  "expectedRevision",
+  "draftPatch",
+  "postId"
+]
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already flag destructive/idempotent/openWorld=false, yet the description adds material behavior: default dry-run semantics, optimistic-concurrency failure condition, returned receipt plus current draft, idempotency via clientRequestId, cost ('Free') and required plan:create scope. This is well beyond what the structured fields convey and does not contradict the destructiveHint—the write is gated behind confirm.

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 tight sentences: what it does first, then the calling contract and preview/commit behavior, then the negative boundaries and cost. No filler, and the most decision-critical fact (dry run unless confirm:true) lands early.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Five parameters with a nested object and no output schema, yet the description covers concurrency, idempotency, dry-run, response contents ('receipt and current draft'), cost and required scope—everything an agent needs to call it correctly and interpret the result.

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 only 40%, but the description names all four required parameters and gives them meaning—'current' expectedRevision as a revision guard, 'stable' clientRequestId as a replay key, draftPatch as the supplied caption/hashtags text. It could go further on the nested patch's partial-update semantics (does omitting caption clear it?).

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 precise verb and resource ('Replace the caption and/or hashtags of one saved draft in Soclo') and explicitly bounds scope ('Does not generate text, change media, schedule, publish or contact social accounts'), so an agent can separate it from save_drafts, reschedule, cancel and work_drafts_edit.

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?

Gives a clear operating procedure: preview when confirm is omitted, act only with confirm:true, and only if the draft is still at expectedRevision. It states exclusions but never names a sibling alternative (e.g. posts_save_drafts or the get_draft tool) or the prerequisite of obtaining postId from soclo_posts_drafts beyond the schema hint.

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

All Soclo toolsInspect
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