Skip to main content
Glama

Soclo

by app.soclo
OverviewDiscussionsAdmin

Save a batch of post drafts

soclo_posts_save_drafts
Idempotent

Create 1-12 new photo-post drafts in Soclo from supplied content: each a new draft id, an owned Library image assetId and its mediaUri, a caption and scheduledFor (kept only as a proposed time). Without confirm:true, previews and saves nothing; with confirm:true, saves the batch once and returns its receipt. Does not overwrite a draft, generate media or captions, schedule, publish or contact social accounts. Keep batchId, draftRevision and clientRequestId for soclo_posts_recover_drafts. Free; needs plan:create.

Input Schema

NameRequiredDescriptionDefault
itemsYes
batchIdYes
confirmNotrue only after the owner approved this exact change. Omit or false for a preview that changes nothing.
draftRevisionYes
clientRequestIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed17 schema fields changed
    • addedInput schema / definitions
      Added value: +{
+  "s1": {
+    "format": "uuid",
+    "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
+    "type": "string"
+  }
+}
    • addedInput schema / properties / batchId / $ref
      Added value: +"#/definitions/s1"
    • removedInput schema / properties / batchId / format
      Removed value: -"uuid"
    • removedInput schema / properties / batchId / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
    • removedInput schema / properties / batchId / type
      Removed value: -"string"
    • addedInput schema / properties / clientRequestId / $ref
      Added value: +"#/definitions/s1"
    • removedInput schema / properties / clientRequestId / format
      Removed value: -"uuid"
    • removedInput schema / properties / clientRequestId / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
    • removedInput schema / properties / clientRequestId / type
      Removed value: -"string"
    • addedInput schema / properties / items / items / properties / assetId / $ref
      Added value: +"#/definitions/s1"
    • removedInput schema / properties / items / items / properties / assetId / format
      Removed value: -"uuid"
    • removedInput schema / properties / items / items / properties / assetId / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
    • removedInput schema / properties / items / items / properties / assetId / type
      Removed value: -"string"
    • addedInput schema / properties / items / items / properties / id / $ref
      Added value: +"#/definitions/s1"
    • removedInput schema / properties / items / items / properties / id / format
      Removed value: -"uuid"
    • removedInput schema / properties / items / items / properties / id / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
    • removedInput schema / properties / items / items / properties / id / type
      Removed value: -"string"
  2. Changed1 schema field 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."
  3. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already cover safety (readOnly=false, destructive=false, idempotent=true, openWorld=false), yet the description still adds non-obvious behavior: dry-run without confirm, single-save semantics with confirm, a returned receipt, and scheduledFor being only a proposed time rather than an actual schedule. The negative-scope list (no media/caption generation, no scheduling, no publishing, no account contact) and the 'Free; needs plan:create' cost/entitlement note are information the agent cannot get from the schema or annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the create action and closed out with cost/entitlement, with no filler sentences. It is a single dense paragraph packing several distinct claims (confirm gate, exclusions, recovery keys, pricing), which is slightly harder to scan than a segmented version would be.

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?

No output schema exists, and the description still tells the agent what comes back (a receipt and the new draft ids) and what to retain for recovery. With a mutating, gated batch operation and sparse schema descriptions, everything needed to call it correctly is present.

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

Parameters5/5

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

Schema coverage is only 20%, and the description compensates by naming confirm's effect, the batchId/draftRevision/clientRequestId triple that must be retained for recovery, and each item field including the crucial clarification that scheduledFor is kept only as a proposed time. That is meaningful semantics beyond the JSON Schema types.

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 specific verb, resource and cardinality: 'Create 1-12 new photo-post drafts in Soclo from supplied content', then enumerates exactly what each draft carries (draft id, owned Library assetId, mediaUri, caption, scheduledFor). It also explicitly separates itself from the closest siblings by saying it 'Does not overwrite a draft' and naming soclo_posts_recover_drafts.

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

Usage Guidelines5/5

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

Gives an explicit decision rule: without confirm:true it previews and saves nothing, with confirm:true it saves the batch once. It also names a follow-up condition (keep batchId, draftRevision and clientRequestId for soclo_posts_recover_drafts) so the agent knows what to do next.

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