Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

getReactions

Read-onlyIdempotent

Retrieves a single reaction by its ID from Follow Up Boss CRM. To list a note's reactions, fetch the note with includeReactions=true.

Instructions

Get ONE reaction by the reaction's own ID. To list a note's reactions, fetch the note with includeReactions=true instead.

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

Input Schema

NameRequiredDescriptionDefault
idYesReaction ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.0.0
    • changedInput schema / properties / id / description
      Previous value: -"Item ID"New value: +"Reaction ID."
    • changedInput schema / properties / id / type
      Previous value: -"number"New value: +"integer"
  2. First observedv1.1.1

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered structurally. The description adds little behavioral detail beyond noting it returns exactly one record; there is no mention of error behavior for missing/unknown IDs and no output schema to lean on.

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?

Two short sentences, zero filler, with the cardinality constraint front-loaded and the alternative path second. Nothing could be removed without losing information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter read tool with full annotation coverage and full schema coverage, the description covers what to pass, how many results to expect, and the main alternative. Only the return shape and not-found behavior are unaddressed, which is minor here.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the schema already says 'Reaction ID', so the baseline is 3. The description adds disambiguating meaning by stressing it is the reaction's *own* ID, guarding against passing a note ID — a real, non-redundant clarification.

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 ONE reaction') and emphasizes single-item scope with 'ONE', which clearly separates it from any list-style retrieval. It does not describe what a reaction record contains, but the purpose is unambiguous.

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

Usage Guidelines4/5

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

Explicitly names the alternative path for the most likely confused use case: 'To list a note's reactions, fetch the note with includeReactions=true instead.' A clear condition selects the alternative, though it frames it around getNote rather than a sibling tool.

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