PostKing MCP Server

template_list

List a brand's content templates with category filters (hook, cta, thread) and detail levels from summaries to full content, ordered by favorites and usage.

Instructions

List the brand's saved content templates. short {id,title,category}; medium adds platforms,isFavorite,bodyPreview (160 chars); full = raw. Pass category to filter (e.g. 'hook', 'cta', 'thread'). Results are ordered by isFavorite desc, then usageCount desc.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "template_list"
  }
}

Input Schema

Name	Required	Description	Default
`detail`	No	Verbosity of returned item(s): "short" = id + primary label + status (cheap list scan); "medium" = key summary fields + counts (a useful glance); "full" = the complete object. Default "short". Lists default to "short" — to zoom into one item, call its get/view tool with detail="medium" or "full".	short
`brandId`	No	Brand ID (defaults to active brand)
`category`	No	Filter templates by category (e.g. 'hook', 'cta', 'thread'). Omit for all.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.7Aug 4, 2026

TDQS

A4.4/5.0

Behavior4/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It reveals the ordering (isFavorite desc, then usageCount desc) and precisely defines the returned fields for each detail level. It doesn't mention pagination or side effects, but the read-only nature is implicit and the ordering/detail disclosures go beyond the schema.

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

Conciseness5/5

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

The description is compact and front-loaded with the primary purpose. Each sentence adds distinct information: purpose, detail variations, filtering, and ordering. There is no redundant or filler content.

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?

No output schema exists, so the description explains return values via detail levels. It covers filtering and ordering. The main gap is no mention of pagination or result limits, which might be relevant for a list operation, but the tool is simple enough that this is not a significant omission.

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?

Schema coverage is 100%, so baseline is 3. The description adds meaning to the detail parameter by spelling out exactly what short/medium/full include, and gives tangible category examples ('hook', 'cta', 'thread'). This goes beyond the schema's enum labels.

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?

The description begins with 'List the brand's saved content templates,' a specific verb+resource phrasing that clearly distinguishes this as a read-only listing tool. It differentiates from sibling template tools (create/update/delete/extract/pick) by focusing on listing and enumerating the detail levels.

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?

The description provides clear usage context: it explains how to filter by category and what the detail parameter controls. It does not explicitly state when to prefer this over alternatives, but the list-oriented nature and the provided filtering guidance make appropriate usage evident.

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

Deploy Server