Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

getTextMessageTemplate

Read-onlyIdempotent

Retrieve a text message template by its ID from Follow Up Boss CRM. Use it to fetch saved SMS content for reuse in communications and follow-up workflows.

Instructions

Get a text message template by ID

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

Input Schema

NameRequiredDescriptionDefault
idYesTemplate ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without description help. The description adds nothing beyond that — no note on not-found behavior, visibility/permission constraints, or whether templates are account-scoped. With annotations doing the work, this is adequate but bare.

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?

One short front-loaded sentence with zero filler, which is appropriate for a one-parameter getter. It is not padded, though its terseness leaves gaps that a slightly longer phrasing could have closed.

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 trivial one-parameter read with full annotation coverage and no output schema, the description is minimally sufficient. It still omits what a template contains and what happens on a missing ID, which an agent calling blindly would want to know.

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% and the single parameter 'id' is documented as 'Template ID'; the description's 'by ID' merely restates it. Baseline 3 applies since the schema carries the parameter semantics.

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?

Names a specific verb ('Get') and resource ('text message template') plus the retrieval key ('by ID'), which distinguishes it from the list operation listTextMessageTemplates. It does not, however, explain how it differs from the sibling getTemplate, so the reader cannot rule out overlap from the text alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: 'by ID' signals a single-record fetch versus the sibling listTextMessageTemplates. There is no explicit statement of when to prefer it over getTemplate or listTextMessageTemplates, and no mention of what to do when the ID is invalid.

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