Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

updateTemplate

DestructiveIdempotent

Update an email template's name, subject, HTML body, and sharing status; merge fields are supported only in the subject and body.

Instructions

Update an email template. Merge fields 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": {
      "id": "<id>"
    },
    "name": "updateTemplate"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesTemplate ID
bodyNoHTML body
nameNoTemplate name
subjectNoEmail subject
isSharedNoShare with other users in the account

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv2.0.0
    • changedInput schema / properties / body / description
      Previous value: -"Body HTML"New value: +"HTML body"
    • addedInput schema / properties / isShared
      Added value: +{
      +  "description": "Share with other users in the account",
      +  "type": "boolean"
      +}
    • changedInput schema / properties / name / description
      Previous value: -"Name"New value: +"Template name"
    • changedInput schema / properties / subject / description
      Previous value: -"Subject"New value: +"Email subject"
  2. First observedv1.1.1

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the mutation profile is covered. The description adds the functional constraint that merge fields resolve only in subject and body, which is genuinely useful and not in the schema or annotations. It does not say whether omitted fields are preserved or cleared, which matters for a destructive update.

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?

Two short sentences with zero filler, and the core action is front-loaded before the merge-field caveat. Nothing could be removed without losing information.

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?

Adequate for a five-parameter update tool whose schema is fully documented and whose safety profile is carried by annotations. Gaps remain: whether the update is partial or full replacement, and the response shape (no output schema exists to cover it).

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 coverage is 100%, so all five parameters are described in the schema; baseline is 3. The description contributes the merge-field applicability rule scoped to subject and body, but says nothing about id semantics or what isShared changes beyond the schema's own wording.

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?

"Update an email template" states a specific verb and resource, and the channel qualifier (email, not text message) separates it from updateTextMessageTemplate in the sibling list. It stops short of naming which sibling to use when, but the action is unambiguous.

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?

There is no explicit when-to-use or when-not guidance, no prerequisites (permissions, template ownership, shared templates), and no routing to alternatives such as createTemplate or mergeTemplate. The verb alone implies context, which is the definition of minimal guidance.

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