Create a new email template for a client's campaigns. Provide the template name and optionally a client ID, HTML page URL, or zip file URL for assets.
Create a new email template for a client
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Template name | |
| client_id | No | Client ID (defaults to CM_CLIENT_ID env var) | |
| html_page_url | No | URL to the HTML page for the template | |
| zip_file_url | No | URL to a zip file containing template assets |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided; the description only says 'Create' without disclosing side effects, required permissions, or behavior on duplicate names. Minimal beyond what the name implies.
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?
Single sentence of 8 words is extremely concise but lacks necessary detail; could be expanded without losing conciseness.
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?
No output schema, no annotations, and the description fails to explain what the tool returns or prerequisite conditions like client existence. Incomplete for practical use.
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% with descriptions for all 4 parameters. The description adds no extra meaning beyond the schema, satisfying the baseline but not improving it.
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 'Create' and the resource 'email template', distinguishing it from sibling tools like copy_template, update_template, delete_template, list_templates.
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 on when to use this tool vs alternatives such as copy_template or when not to use it. Lacks any context about prerequisites or situation.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/pauliowest/cmon-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server