Skip to main content
Glama
DynamicEndpoints

Advanced PocketBase MCP Server

send_templated_email

Send personalized emails using predefined templates within PocketBase databases to automate communication workflows.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The async handler function for the 'send_templated_email' MCP tool. It lazy-loads the EmailService, calls sendTemplatedEmail with validated parameters, handles errors, and returns a structured response with the email log details.
    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}`);
      }
    }
  • Registers the 'send_templated_email' tool on the MCP server, providing description and Zod-based input schema for validation.
    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 input schema defining parameters for the send_templated_email tool: template name, recipient email, optional sender/from, custom subject, and variables object.
      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')
    }
  • Core EmailService method implementing templated email sending: fetches template from PocketBase, compiles Handlebars templates with variables, sends via nodemailer Transporter, creates success/failure log in 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}`);
      }
    }
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

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

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