Skip to main content
Glama
DynamicEndpoints

pocketbase-mcp-server

send_templated_email

Simplifies email automation by sending templated emails through the PocketBase MCP server. Ideal for managing personalized communication workflows efficiently.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Core handler function in EmailService class that implements the templated email sending logic: retrieves template from PocketBase, compiles with Handlebars using variables, sends via nodemailer, logs success/failure to email_logs collection.
    async sendTemplatedEmail(data: {
      template: string;
      to: string;
      from?: string;
      variables?: Record<string, any>;
      customSubject?: string;
    }): Promise<EmailLog> {
      try {
        // Get template
        const template = await this.getTemplate(data.template);
        
        // Compile templates
        const subjectTemplate = Handlebars.compile(data.customSubject || template.subject);
        const htmlTemplate = Handlebars.compile(template.htmlContent);
        const textTemplate = template.textContent ? Handlebars.compile(template.textContent) : null;
    
        // Apply variables
        const variables = data.variables || {};
        const subject = subjectTemplate(variables);
        const html = htmlTemplate(variables);
        const text = textTemplate ? textTemplate(variables) : undefined;
    
        // Send email
        const info = await this.transporter.sendMail({
          from: data.from || process.env.SMTP_USER || process.env.DEFAULT_FROM_EMAIL,
          to: data.to,
          subject,
          html,
          text,
        });      // Log email
        const emailLog = await this.pb.collection('email_logs').create({
          to: data.to,
          from: data.from || process.env.SMTP_USER || process.env.DEFAULT_FROM_EMAIL,
          subject,
          template: data.template,
          status: 'sent',
          variables: variables,
        });
    
        return emailLog as unknown as EmailLog;
      } catch (error: any) {
        // Log failed email
        const emailLog = await this.pb.collection('email_logs').create({
          to: data.to,
          from: data.from || process.env.SMTP_USER || process.env.DEFAULT_FROM_EMAIL,
          subject: data.customSubject || 'Email send failed',
          template: data.template,
          status: 'failed',
          error: error.message,
          variables: data.variables || {},
        });
    
        throw new Error(`Failed to send email: ${error.message}`);
      }
    }
  • MCP server.tool registration for 'send_templated_email' including Zod inputSchema, description, and thin wrapper handler that lazy-loads EmailService and delegates to its sendTemplatedEmail method.
    this.server.tool(
      'send_templated_email',
      {
        description: 'Send a templated email using the configured email service',
        inputSchema: {
          template: z.string().describe('Email template name'),
          to: z.string().email().describe('Recipient email address'),
          from: z.string().email().optional().describe('Sender email address'),
          subject: z.string().optional().describe('Custom email subject'),
          variables: z.record(z.unknown()).optional().describe('Template variables')
        }
      },
      async ({ template, to, from, subject, variables }) => {
        // Lazy load Email service
        await this.ensureEmailService();
        
        if (!this.emailService) {
          throw new Error('Email service not available. Please configure EMAIL_SERVICE or SMTP settings.');
        }
    
        try {
          const result = await this.emailService.sendTemplatedEmail({
            template,
            to,
            from,
            customSubject: subject,
            variables
          });
          return {
            content: [{
              type: 'text',
              text: JSON.stringify({
                success: true,
                emailLog: {
                  id: result.id,
                  to: result.to,
                  subject: result.subject,
                  status: result.status,
                  sentAt: result.created
                }
              }, null, 2)
            }]
          };
        } catch (error: any) {
          throw new Error(`Failed to send email: ${error.message}`);
        }
      }
    );
  • Zod inputSchema defining parameters for send_templated_email tool: template name, recipient email, optional sender/from, custom subject, and variables object.
    {
      description: 'Send a templated email using the configured email service',
      inputSchema: {
        template: z.string().describe('Email template name'),
        to: z.string().email().describe('Recipient email address'),
        from: z.string().email().optional().describe('Sender email address'),
        subject: z.string().optional().describe('Custom email subject'),
        variables: z.record(z.unknown()).optional().describe('Template variables')
  • Supporting helper method to retrieve EmailTemplate from PocketBase by name, used by sendTemplatedEmail.
    async getTemplate(name: string): Promise<EmailTemplate> {
      try {
        const template = await this.pb.collection('email_templates')
          .getFirstListItem(`name="${name}"`);
        
        return template as unknown as EmailTemplate;
      } catch (error: any) {
        throw new Error(`Template not found: ${name}`);
      }
    }
Behavior1/5

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

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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

Related 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/DynamicEndpoints/pocketbase-mcp-server'

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