Skip to main content
Glama

get_template

Retrieve template details and HTML content from Mailchimp for email campaign management and content reuse.

Instructions

Get a template's details and HTML content.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
template_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The implementation of the get_template tool, which retrieves template details and HTML content via the Mailchimp client.
    @mcp.tool()
    async def get_template(template_id: int) -> str:
        """Get a template's details and HTML content."""
        mc = get_client()
        t = await mc.get(f"/templates/{template_id}")
        return _fmt({
            "id": t.get("id", ""),
            "name": t.get("name", ""),
            "type": t.get("type", ""),
            "active": t.get("active", False),
            "html": t.get("html", "")[:5000],
            "created_at": t.get("date_created", ""),
            "edited_at": t.get("date_edited", ""),
        })
Behavior2/5

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

With no annotations provided, the description carries full burden but only states what the tool does without behavioral details. It doesn't disclose if this is a read-only operation, requires authentication, has rate limits, or what happens on errors, which are critical for a tool that retrieves data.

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 a single, efficient sentence that directly states the tool's function without unnecessary words. It's front-loaded and wastes no space, making it easy to parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has an output schema (which handles return values) and only one parameter, the description is minimally complete but lacks depth. For a data retrieval tool with no annotations, it should ideally mention safety or behavioral aspects to better guide the agent.

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 0%, so the description must compensate, but it adds no parameter information beyond what the schema implies. The description doesn't explain what 'template_id' represents or its format, though with only one parameter and an output schema, the baseline is adequate but not helpful.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Get' and the resource 'template's details and HTML content', making the purpose understandable. However, it doesn't distinguish this from sibling tools like 'list_templates' or 'get_campaign_content', which would require explicit differentiation for a score of 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. There are no mentions of prerequisites, when-not-to-use scenarios, or comparisons to siblings like 'list_templates' for broader queries, leaving the agent without contextual usage cues.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/AlexlaGuardia/mcp-mailchimp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server