Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

listTemplates

Read-onlyIdempotent

Retrieve email templates from Follow Up Boss CRM with pagination controls for selecting reusable messages.

Instructions

List email 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": "listTemplates"
  }
}

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.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. The description adds nothing beyond that: no word on pagination behavior (cursor vs. offset), default page size, or result ordering, which is the kind of context a list tool should supply.

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?

Three words, front-loaded, zero waste. It is efficient, though the brevity is more under-specification than disciplined conciseness.

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 simple read-only list tool with complete parameter documentation and annotations covering safety, the description is minimally sufficient. It omits what a template contains and how the two pagination styles (next vs. offset) should be chosen, which leaves real gaps for an agent operating near the sibling listTextMessageTemplates.

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 all three pagination parameters (next, limit, offset) are already documented in the schema. The description adds no meaning about how cursor-based pagination interacts with offset, so the baseline 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 (list email templates), which is unambiguous on its own. It doesn't distinguish itself from the sibling listTextMessageTemplates, which an agent could easily confuse it with when looking for text/SMS templates.

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 tool, when to use listTextMessageTemplates or getTemplate instead, or what prerequisites apply. The agent must infer usage purely 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