easysociable-mcp

List authoring drafts

list_template_drafts

Read-onlyIdempotent

List all template authoring drafts for the current account owner, including validation status, name, and timestamps. Use draft IDs to resume, update, or publish sessions.

Instructions

List all template authoring drafts for the current account owner. Returns draft summaries with validation status, name, and timestamps. Use to resume an authoring session or discover draft IDs before updating or publishing. Alternatives: Use get_template_draft when you have a draftId to inspect full layer AST. Read-only query scoped to account owner.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`drafts`	No	Array of draft summary objects.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.1.17Oct 5, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "drafts": {
+      "description": "Array of draft summary objects.",
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

Addedv0.1.15Oct 5, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and closed-world scope. The description adds value beyond that by specifying the account-owner scoping and previewing the returned summary fields (validation status, name, timestamps). It does not cover pagination or ordering behavior, which would be the remaining useful detail for a list tool.

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?

Four sentences, each earning its place, with the core action front-loaded. The trailing 'Read-only query scoped to account owner' partially restates the readOnlyHint annotation, but the account-owner scoping is new information, so the redundancy is minor.

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?

For a zero-parameter, read-only list tool with full annotation coverage and an output schema, the description covers everything an agent needs: what is returned, why to call it, and which sibling to prefer when a draftId is known. Return-value details are appropriately left to the output schema.

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?

The tool takes zero parameters, so there is no parameter semantics to document and the baseline of 4 applies. The description correctly does not invent filtering options that the empty schema cannot support.

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 ('List all template authoring drafts') and immediately narrows scope to 'the current account owner'. It distinguishes itself from the sibling get_template_draft by explicitly calling out that the latter is for a known draftId and returns the full layer AST.

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 two concrete use cases ('resume an authoring session' and 'discover draft IDs before updating or publishing') and names the alternative tool plus the condition that selects it. An agent can route between list and get without opening either schema.

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