Skip to main content
Glama

fluentcrm_create_email_template

Create email templates for marketing campaigns by defining title, subject, and HTML content to streamline communication workflows.

Instructions

Tworzy nowy szablon email

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesNazwa szablonu
subjectYesTemat
bodyYesTreść HTML

Implementation Reference

  • MCP tool handler: extracts arguments and calls FluentCRMClient.createEmailTemplate, formats response as JSON text.
    case 'fluentcrm_create_email_template':
      return { content: [{ type: 'text', text: JSON.stringify(await client.createEmailTemplate(args as any), null, 2) }] };
  • Core helper method in FluentCRMClient: sends POST request to /email-templates API endpoint with input data.
    async createEmailTemplate(data: any) {
      const response = await this.apiClient.post('/email-templates', data);
      return response.data;
    }
  • Input schema validation: requires title, subject, body for email template creation.
    inputSchema: {
      type: 'object',
      properties: {
        title: { type: 'string', description: 'Nazwa szablonu' },
        subject: { type: 'string', description: 'Temat' },
        body: { type: 'string', description: 'Treść HTML' },
      },
      required: ['title', 'subject', 'body'],
    },
  • Tool registration in ListToolsResponse: defines name, description, and input schema.
    {
      name: 'fluentcrm_create_email_template',
      description: 'Tworzy nowy szablon email',
      inputSchema: {
        type: 'object',
        properties: {
          title: { type: 'string', description: 'Nazwa szablonu' },
          subject: { type: 'string', description: 'Temat' },
          body: { type: 'string', description: 'Treść HTML' },
        },
        required: ['title', 'subject', 'body'],
      },
    },
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 it 'creates' without disclosing behavioral traits. It doesn't mention permissions needed, whether creation is idempotent, what happens on duplicate titles, or what the response contains. For a creation tool with zero annotation coverage, this is inadequate.

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 in Polish that directly states the tool's purpose with zero wasted words. It's appropriately front-loaded and perfectly concise for its simple function.

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

Completeness2/5

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

For a creation tool with no annotations and no output schema, the description is insufficient. It doesn't explain what happens after creation, whether the template becomes immediately available, what format the body should be in beyond 'HTML', or how this interacts with other FluentCRM components. The context demands more completeness.

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%, so the schema already documents all three parameters (title, subject, body) with Polish descriptions. The description adds no additional parameter information beyond what's in the schema, meeting the baseline for high schema coverage.

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 'Tworzy nowy szablon email' (Creates a new email template) clearly states the action (creates) and resource (email template) in Polish. It's specific enough to understand the basic function, though it doesn't explicitly differentiate from sibling tools like 'fluentcrm_create_campaign' or 'fluentcrm_create_automation' which also create resources.

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's no mention of prerequisites, when email templates are needed, or how this relates to sibling tools like 'fluentcrm_list_email_templates' or 'fluentcrm_create_campaign'.

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/netflyapp/fluentcrm-mcp-server'

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