Skip to main content
Glama

fluentcrm_list_email_templates

Retrieve email templates from FluentCRM to use in marketing campaigns and communications.

Instructions

Pobiera szablony email

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Tool registration in the MCP tools list, including name, description, and input schema (no parameters required).
      name: 'fluentcrm_list_email_templates',
      description: 'Pobiera szablony email',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • MCP server request handler for tool calls. Matches the tool name and delegates execution to client.listEmailTemplates(), formatting the result as JSON text response.
    case 'fluentcrm_list_email_templates':
      return { content: [{ type: 'text', text: JSON.stringify(await client.listEmailTemplates(), null, 2) }] };
  • Core implementation in FluentCRMClient class: makes a GET request to the '/email-templates' API endpoint and returns the data.
    async listEmailTemplates(params: any = {}) {
      const response = await this.apiClient.get('/email-templates', { params });
      return response.data;
    }
  • Input schema definition: empty object (no input parameters).
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Retrieves' implies a read-only operation, but it doesn't specify whether this returns all templates, supports pagination, includes metadata, or has any access restrictions. For a list tool with zero annotation coverage, this is a significant gap in transparency.

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 phrase ('Pobiera szablony email') that directly states the purpose without any wasted words. It's appropriately sized and front-loaded, making it easy for an agent 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's simplicity (0 parameters, no output schema, no annotations), the description is minimally adequate but lacks depth. It doesn't explain what 'retrieves' entails (e.g., format, scope, or limitations), which could be important for a list operation. For a basic read tool, it's functional but not comprehensive.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has 0 parameters, and schema description coverage is 100% (empty schema). The description doesn't need to explain any parameters, so it meets the baseline of 4 for zero-parameter tools, as there's no additional semantic burden to cover.

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 'Pobiera szablony email' (Polish for 'Retrieves email templates') clearly states the verb 'retrieves' and the resource 'email templates', which is specific and actionable. However, it doesn't distinguish this tool from sibling list tools like fluentcrm_list_automations or fluentcrm_list_campaigns, which follow a similar pattern but for different 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 (e.g., needing email templates to exist), exclusions, or comparisons to other list tools in the sibling set, leaving the agent to infer usage based on the tool name alone.

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