easysociable-mcp

List templates

list_templates

Read-onlyIdempotent

Browse public template catalog summaries and filter by platform, role, density, canvas preset, or image needs to find social carousel and slideshow layouts.

Instructions

List public template catalog summaries from Gateway (filterable by platform, role, density, canvasPreset). For Slideshow page template selection, prefer recommend_slideshow_templates. Alternatives: Use get_template to inspect specific slot requirements. Read-only catalog query.

Input Schema

TableJSON Schema

Name	Required	Description
`q`	No	Search term matching template name or description.
`all`	No	Fetch all matching templates across pages.
`limit`	No	Max items per page.
`roles`	No	Narrative role filter: hook \| value \| rehook \| cta
`cursor`	No	Pagination cursor from previous nextCursor.
`locale`	No	Language/locale code (e.g. en, zh-CN).
`density`	No	Density filter: sparse \| normal \| dense
`platforms`	No	Platform filter: tiktok \| linkedin \| instagram \| threads \| xiaohongshu
`canvasPreset`	No	Aspect ratio preset (e.g. 9:16, 4:5, 1:1, 3:4).
`contentFamily`	No	Content family filter.
`requiresImage`	No	Filter templates that require an image slot.
`contentArchetypes`	No	Content archetypes list.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`templates`	No	Template summaries.
`nextCursor`	No	Cursor for next page.

Schema Changelog

Changes observed during successful MCP inspections.

Changed13 schema fields changedv0.1.17Oct 5, 2026

addedInput schema / properties / all / description

Added value: +"Fetch all matching templates across pages."

addedInput schema / properties / canvasPreset / description

Added value: +"Aspect ratio preset (e.g. 9:16, 4:5, 1:1, 3:4)."

addedInput schema / properties / contentArchetypes / description
```
Added value: +"Content archetypes list."
```
addedInput schema / properties / contentFamily / description
```
Added value: +"Content family filter."
```

addedInput schema / properties / cursor / description

Added value: +"Pagination cursor from previous nextCursor."

addedInput schema / properties / density / description

Added value: +"Density filter: sparse | normal | dense"

addedInput schema / properties / limit / description
```
Added value: +"Max items per page."
```

addedInput schema / properties / locale / description

Added value: +"Language/locale code (e.g. en, zh-CN)."

addedInput schema / properties / platforms / description

Added value: +"Platform filter: tiktok | linkedin | instagram | threads | xiaohongshu"

addedInput schema / properties / q / description

Added value: +"Search term matching template name or description."

addedInput schema / properties / requiresImage / description

Added value: +"Filter templates that require an image slot."

addedInput schema / properties / roles / description

Added value: +"Narrative role filter: hook | value | rehook | cta"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "nextCursor": {
+      "description": "Cursor for next page.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "templates": {
+      "description": "Template summaries.",
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

First observedv0.1.13Oct 5, 2026

TDQS

A4.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered; the closing 'Read-only catalog query' largely repeats that. The one genuinely additive behavioral signal is that returns are 'summaries', implying detail must come from get_template, but no pagination or result-size behavior is described.

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 short sentences, front-loaded with the verb and resource, then routing. The trailing 'Read-only catalog query' is redundant against readOnlyHint and is the only wasted clause.

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 shape need not be explained, all 12 params are documented in the schema, and the description supplies the routing context an agent needs to pick this tool over its alternatives. Nothing essential is missing for a filtered, paginated read-only list.

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 description coverage is 100% across 12 params, so the schema already documents every filter, including enums-in-text for roles, density and platforms. The description only names four of those dimensions (platform, role, density, canvasPreset), adding no syntax or semantics beyond the schema, so baseline 3 applies.

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 with scope: 'List public template catalog summaries from Gateway', and enumerates the filterable dimensions. It also draws the boundary against get_template for full slot requirements and against recommend_slideshow_templates for slideshow page selection, so an agent can distinguish it from siblings without opening a 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?

Explicit routing: prefer recommend_slideshow_templates for Slideshow page template selection, and use get_template to inspect specific slot requirements. The condition that selects each alternative is named, leaving little to inference.

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