Skip to main content
Glama

List post templates

clipember_list_templates
Read-onlyIdempotent

Show the user's post templates — saved editor setups (captions, accounts, YouTube and Instagram settings, tags). Use one to fill a clipember_create_post call. Templates never contain TikTok's audience, interaction or disclosure choices: pass them per post in tiktokOptions only when the user told you them for that post, or the TikTok post waits for the user in the TikTok queue.

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": "clipember_list_templates"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the bar is lower; the description still adds real value by disclosing a data-completeness limit (templates never carry TikTok audience/interaction/disclosure choices) and the consequence of omitting them (the post sits in the TikTok queue). It does not cover ordering or empty-list behavior, but nothing contradicts the annotations.

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?

Two sentences, front-loaded with what the tool returns before moving to how to use it. The second sentence is long and carries TikTok-specific rules that arguably belong with create_post, but it earns its place by preventing a common downstream error.

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?

With no output schema and no parameters, the description compensates by enumerating what a template contains, which gives the agent a usable picture of the return shape. Minor gaps remain around ordering or what an empty result looks like, but nothing essential to invoking it correctly is missing.

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 the baseline is 4. The discussion of tiktokOptions belongs to the consuming create_post call rather than this tool, but it is clearly framed as cross-tool guidance and does not misrepresent this schema.

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 ("Show the user's post templates") and then defines what a template actually is: saved editor setups covering captions, accounts, YouTube/Instagram settings, and tags. No sibling tool lists templates, so there is no ambiguity to resolve.

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?

Explicitly routes the output downstream: "Use one to fill a clipember_create_post call," naming the sibling that consumes the result. It also gives a clear when/when-not rule for TikTok fields — pass them per post only when the user stated them for that post, otherwise the post waits in the TikTok queue.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources