Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

createTextMessageTemplate

Creates a reusable text message template with a name and message body, optionally shared with other users in the Follow Up Boss account.

Instructions

Create 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": {
      "name": "<name>",
      "message": "<message>"
    },
    "name": "createTextMessageTemplate"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesTemplate name
messageYesText message body (merge fields allowed)
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": "Message 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 (merge fields allowed)",
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "name",
      -  "body"
      -]New value: +[
      +  "name",
      +  "message"
      +]
  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 state this is a non-destructive, non-idempotent write (readOnlyHint=false, destructiveHint=false, idempotentHint=false), so the description adds little. It omits the behavior that matters for a create call: whether duplicates are rejected, what is returned on success, how isShared defaults, and whether merge fields are validated. Only a pointer to the message field is provided.

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. The second sentence is largely redundant with the schema, keeping it from a 5, but there is no padding or ambiguity.

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?

The tool is simple (3 flat params, fully documented, no output schema, annotations present), so the description is minimally sufficient to invoke it correctly. It nonetheless leaves the create-vs-createTemplate ambiguity and post-creation behavior unexplained, which is a meaningful gap in this crowded sibling set.

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 name, message, and isShared are already documented in the input schema (including that merge fields are allowed). The description's note that 'Message text goes in `message`' merely restates the schema and adds no new semantics, so the baseline of 3 applies.

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: 'Create a text message template.' An agent can tell what is produced. It does not, however, differentiate this tool from the generic sibling createTemplate (or from createTextMessage/createTemplate in the wider family), so sibling routing is left to inference.

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 guidance on when to use this instead of createTemplate, listTextMessageTemplates, or updateTextMessageTemplate. No prerequisites, no mention of what happens if a template with the same name exists. The agent must infer usage entirely from the name.

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