easysociable-mcp

Get template

get_template

Read-onlyIdempotent

Retrieve a published template's details and public slots table to bind slide copy for slideshows or inspect constraints before creating a run.

Instructions

Get one published template detail including the public slots[] table (key, type, required, constraints). Use slots to bind slide copy in create_slideshow_run or inspect template constraints. Alternatives: Use list_templates to browse catalog. Read-only catalog query.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`templateId`	Yes	The unique published template identifier to retrieve.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`id`	No	Published template ID.
`slots`	No	Public slots table.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.1.17Oct 5, 2026

addedInput schema / properties / templateId / description

Added value: +"The unique published template identifier to retrieve."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "id": {
+      "description": "Published template ID.",
+      "type": "string"
+    },
+    "slots": {
+      "description": "Public slots table.",
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

First observedv0.1.13Oct 5, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered structurally. The description adds real value beyond that by disclosing what the payload contains (the public slots[] table with key, type, required, constraints) and restating the read-only catalog nature.

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?

Three sentences, no filler, and the core purpose and return content are front-loaded before the alternatives clause. Slightly dense with parenthetical detail but nothing is wasted.

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?

An output schema exists, so return-value documentation is not strictly required, yet the description still signals the slots structure and its binding use case. Combined with full annotation coverage, an agent has everything needed 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?

Only one parameter with 100% schema description coverage ('The unique published template identifier to retrieve.'), so the schema carries the semantics. The description adds nothing about the identifier's format or where to obtain it, which is the baseline-3 case.

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 ('Get one published template detail') and immediately scopes the return to the public slots[] table. The 'published' qualifier separates it from get_template_draft and list_template_drafts in the sibling set.

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 concrete downstream usage ('Use slots to bind slide copy in create_slideshow_run or inspect template constraints') and names an alternative ('Use list_templates to browse catalog'). It does not clarify when to prefer this over get_template_draft, but the browse-vs-fetch distinction is explicit.

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