Skip to main content
Glama
agentisend

agentisend

List templates

list_templates
Read-onlyIdempotent

Lists email templates on the account with each template's live published version, showing which are ready to send.

Instructions

Purpose: see the templates on this account and which version of each is live. NOT for: rendering one (render_template) or making a draft live (publish_template). Returns: each template with its current published version number. One with no published version cannot be sent yet.

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

Input Schema

NameRequiredDescriptionDefault
limitNoPage size (1-100).
cursorNonext_cursor from the previous page. Omit for the first page.

Output Schema

NameRequiredDescriptionDefault
dataNoThis page of rows.
errorNoPresent instead of the fields above when the call was refused: code, message, fix, docs_url, retryable and, when waiting helps, retry_after_seconds.
has_moreNoTrue when another page follows.
next_cursorNoPass back as cursor for the next page; null on the last page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/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 openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral context: templates lacking a published version 'cannot be sent yet', which is a state-dependent operational constraint not present in annotations or 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?

Three labeled clauses (Purpose / NOT for / Returns) with zero filler. Constraints and routing information are front-loaded, and every sentence carries actionable content.

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?

Output schema exists so return values need not be spelled out, yet the description adds the one semantic detail that matters (published-version presence). Annotations cover safety, schema covers pagination — nothing an agent needs to call this correctly is missing.

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% with only two pagination parameters (limit, cursor), both fully documented in the schema. The description adds no parameter-level meaning, so the 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 and resource ('see the templates on this account and which version of each is live') and explicitly separates itself from render_template and publish_template. An agent can distinguish it from the ~45 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?

The 'NOT for' clause names both alternatives by exact tool name and the action each performs, giving explicit when-not guidance rather than implied context. Combined with the purpose statement, selection is unambiguous.

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