Skip to main content
Glama
murphywuwu

easysociable-mcp

by murphywuwu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Publish authoring draft

publish_template_draft

Validate a finalized authoring draft and publish it to the public or workspace template catalog, promoting it to an immutable template ready for slideshow runs.

Instructions

Validate and publish an authoring draft into the public or workspace template catalog. Call when draft design and slot contracts are finalized and ready for instantiation in slideshow runs. If still editing or fixing layout rules, use update_template_draft. To inspect validation before publishing, use get_template_draft. Promotes draft to an immutable published template. Validates AST against layout rules; fails if required slots or constraints are violated. Returns published Template entity with public templateId, slots table, and catalog status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
draftIdYesThe unique draft identifier to validate and publish.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoPublished template ID.
slotsNoPublic slots table.
statusNoCatalog status (published).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.17
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "id": {
+      "description": "Published template ID.",
+      "type": "string"
+    },
+    "slots": {
+      "description": "Public slots table.",
+      "type": "array"
+    },
+    "status": {
+      "description": "Catalog status (published).",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  2. Changed1 schema field changedv0.1.16
    • addedInput schema / properties / draftId / description
      Added value: +"The unique draft identifier to validate and publish."
  3. First observedv0.1.13

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, idempotentHint=false, destructiveHint=false), the description discloses non-obvious traits: publication is an immutable promotion, the AST is validated against layout rules, and the call fails when required slots/constraints are violated. That validation-failure and irreversibility context is exactly what annotations cannot convey.

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 purpose and routing before behavioral detail, and every sentence carries information. The final sentence describing the returned Template entity, templateId, slots table, and catalog status partially duplicates the output schema, which is a minor redundancy.

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?

An output schema exists, so return values needn't be explained, and the description still adds the validation/failure semantics and immutability caveat. For a one-parameter mutation with annotations present, this is complete enough for an agent to call it correctly.

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% for the single draftId parameter, so the schema already documents it fully. The description adds only the implicit notion that the draft is validated, not new syntax or format detail. Baseline 3 applies when the schema does the heavy lifting.

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 and resource ('Validate and publish an authoring draft into the public or workspace template catalog') and immediately distinguishes itself from siblings by naming update_template_draft and get_template_draft. An agent can tell it apart from other template tools without opening any schema.

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 trigger ('when draft design and slot contracts are finalized and ready for instantiation'), an explicit exclusion ('If still editing or fixing layout rules, use update_template_draft'), and an inspection alternative ('use get_template_draft'). Nothing is left to inference.

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