Retrieve all starter-gallery email templates available to your workspace. Access pre-designed templates for quick email creation.
List starter-gallery email templates available to every workspace.
| Name | Required | Description | Default |
|---|---|---|---|
| apiKey | No | Send16 API key (overrides SEND16_API_KEY env var) |
Changes observed during successful MCP inspections.
v0.5.7Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must convey behavioral traits. It only says 'list', which is implicitly read-only, but does not disclose authentication requirements (apiKey parameter), rate limits, or that it returns a list of templates. The minimal description lacks transparency beyond the obvious.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single concise sentence with no extraneous information. However, it could be restructured to include more detail without losing conciseness. For a simple tool, it is efficient but perhaps too minimal for full clarity.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool has no output schema, so the description should explain what is returned (e.g., list of templates, structure). It does not mention return format, pagination, or whether the apiKey is required. With 1 optional parameter and no annotations, the description is incomplete for an agent to use confidently.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% (only apiKey parameter), and the schema already describes its purpose. The description adds no additional meaning about the parameter. With high coverage, the baseline is 3, and the description does not improve or clarify parameter usage.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb 'list' and the resource 'starter-gallery email templates', with the scope 'available to every workspace'. This distinguishes it from other list tools like list_campaigns or list_contacts, and from get_template which retrieves a single template.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives. For example, there is no mention of when to use list_templates instead of get_template, or how it differs from other list tools. The agent receives no context about prerequisites or scenarios.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.