Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

listTextMessageTemplates

Read-onlyIdempotent

Retrieve paginated text message templates from Follow Up Boss CRM to review reusable SMS content and choose templates for outreach.

Instructions

List text message templates

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "listTextMessageTemplates"
  }
}

Input Schema

NameRequiredDescriptionDefault
nextNoCursor for next page of results
limitNoMaximum number of results to return
offsetNoOffset for pagination

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

C2.6/5.0
Behavior2/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 covered structurally. The description adds nothing beyond that — no note on result volume, pagination behavior, ordering, or permission requirements — so it contributes no behavioral context of its own.

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?

A single short sentence with zero filler, front-loaded and unambiguous. It earns its brevity, though the brevity borders on under-specification rather than deliberate economy.

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?

There is no output schema, so the description is the only place an agent could learn what a listed template contains or how pages are returned, and it says nothing. For a paginated list tool with three parameters and no return-value documentation, this leaves a real gap.

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 `next`, `limit`, and `offset` are each documented in the schema, which sets the baseline at 3. The description does not clarify the interaction between the cursor and offset-based pagination, but it is not required to when the schema is this complete.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description restates the name almost verbatim: a list operation on text message templates. The verb "List" implicitly separates it from createTextMessageTemplate, getTextMessageTemplate, and updateTextMessageTemplate, but nothing is said about what a text message template is or how it differs from the generic listTemplates sibling.

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 when-to-use guidance is given, and no alternative is named. An agent cannot tell from the description whether to call this or the sibling listTemplates, nor how to choose between the `next` cursor and `limit`/`offset` pagination styles.

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