Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

updateTextMessageTemplate

DestructiveIdempotent

Modify an existing text message template by ID, including its name, message body, and sharing setting, to keep Follow Up Boss SMS content current.

Instructions

Update a text message template. Message text goes in message.

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": "updateTextMessageTemplate"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesTemplate ID
nameNoTemplate name
messageNoText message body
isSharedNoShare with other users in the account

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

C2.9/5.0
Behavior2/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 safety-relevant traits are covered structurally. The description adds nothing beyond that: it does not say whether this is a partial or full replacement, what happens to unspecified fields, which permissions are needed, or that destruction is possible. The lone sentence about `message` duplicates schema information.

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, front-loaded sentences with no filler. It is efficient, though the second sentence spends space on redundant schema mapping rather than useful behavior.

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

Completeness2/5

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

For a destructive, non-read-only mutation with four parameters and no output schema, the description is too thin. It omits partial-vs-full-update semantics, side effects of sharing changes via isShared, and any confirmation or permission expectations, leaving real ambiguity about what an update call does.

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% with all four parameters individually described, so the schema carries the parameter burden. The description's note that message text goes in `message` merely restates the schema and adds no format or constraints (length limits, HTML handling, etc.), making baseline 3 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?

The description gives a specific verb and resource ('Update a text message template'), which is clearly distinct from create/get/list/merge text message template siblings. However, it never differentiates this from the generic updateTemplate or mergeTemplate siblings that appear in the list.

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 when-to-use guidance, no mention of when to prefer mergeTextMessageTemplate or updateTemplate, and no prerequisite information. An agent must infer all selection logic from the name alone.

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