Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

getTemplate

Read-onlyIdempotent

Retrieves an email template by its ID so you can inspect or reuse existing template content.

Instructions

Get an email 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": "getTemplate"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesTemplate ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare this a read-only, idempotent, non-destructive, closed-world operation, so the safety profile is fully covered. The description contributes only the qualifier that the template is an email template, adding no context on not-found behavior or data returned.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with zero filler. There is nothing to trim and the identifying information appears immediately.

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?

A simple one-parameter read tool with full annotation coverage needs little, but with no output schema the description could have disclosed what a template object contains or what happens when the ID is unknown. As written it is adequate but leaves those gaps unfilled.

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 is typed as a number with the label "Template ID", so the schema does the work. The description's "by ID" restates the schema without adding format, source, or validity guidance.

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?

States a specific verb and resource ("Get an email template by ID"), which is clearly distinguishable from createTemplate/updateTemplate/mergeTemplate. However it does not differentiate itself from listTemplates or getTextMessageTemplate, both of which an agent could plausibly pick instead.

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 explicit guidance on when to use this versus listTemplates (to discover IDs) or getTextMessageTemplate (for the SMS variety). The phrase "by ID" implicitly signals a single-record fetch, but the agent is left to infer prerequisites such as where the ID comes from.

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