Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

createTemplate

Create email templates with merge fields in the subject and body, and optionally share them with other users in the account.

Instructions

Create an email template. Merge fields (e.g. %contact_first_name%) work only in subject and body.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>",
      "subject": "<subject>",
      "body": "<body>"
    },
    "name": "createTemplate"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesHTML body (merge fields allowed)
nameYesTemplate name
subjectYesEmail subject (merge fields allowed)
isSharedNoShare with other users in the account

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.0.0
    • changedInput schema / properties / body / description
      Previous value: -"Email body HTML"New value: +"HTML body (merge fields allowed)"
    • addedInput schema / properties / isShared
      Added value: +{
      +  "description": "Share with other users in the account",
      +  "type": "boolean"
      +}
    • changedInput schema / properties / subject / description
      Previous value: -"Email subject"New value: +"Email subject (merge fields allowed)"
  2. First observedv1.1.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare non-read-only, non-destructive, non-idempotent, closed-world behavior. The description adds one genuinely useful constraint beyond them: merge fields are scoped to subject and body only (implying they do NOT expand in the name). It says nothing about name uniqueness/collision behavior, permissions, or what is returned after creation.

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

Conciseness4/5

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

Two short sentences, front-loaded with the action and then the key constraint; nothing extraneous. Slight redundancy with the schema's per-field merge-field notes keeps it from a 5.

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?

For a creation tool with no output schema and four parameters, the definition omits meaningful information: whether the response includes the new template's ID, whether the name must be unique, and what permissions are needed. Adequate but with clear gaps.

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 all four parameters are documented in the schema itself. The description's merge-field note merely reinforces the schema's "merge fields allowed" wording and adds the "only" scoping nuance; baseline 3 is appropriate.

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?

States a specific verb and resource ("Create an email template"), and the "email" qualifier implicitly separates it from the sibling createTextMessageTemplate. It falls short of explicitly naming that sibling or stating scope, so it stops at a clear-but-undifferentiated 4.

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?

No guidance on when to use this versus updateTemplate, mergeTemplate, or createTextMessageTemplate, and no prerequisites or exclusions. The usage context is only inferable from the verb.

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

Deploy Server

Other Tools