Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

createReaction

Add an emoji reaction to a Note, Call, or ThreadedReply as the API key owner to acknowledge CRM items via the Follow Up Boss beta endpoint.

Instructions

Add an emoji reaction to a Note, Call or ThreadedReply as the API key owner. Beta endpoint.

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": {
      "refType": "<refType>",
      "refId": "<refId>"
    },
    "name": "createReaction"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNoSingle-character emoji, e.g. a thumbs up.
refIdYesID of the item being reacted to.
refTypeYesType of item reacted to.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv2.0.0
    • addedInput schema / properties / body
      Added value: +{
      +  "description": "Single-character emoji, e.g. a thumbs up.",
      +  "type": "string"
      +}
    • removedInput schema / properties / emoji
      Removed value: -{
      -  "description": "Emoji reaction",
      -  "type": "string"
      -}
    • changedInput schema / properties / refId / description
      Previous value: -"Reference ID"New value: +"ID of the item being reacted to."
    • changedInput schema / properties / refId / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / refType / description
      Previous value: -"Reference type (e.g. note, email)"New value: +"Type of item reacted to."
    • addedInput schema / properties / refType / enum
      Added value: +[
      +  "Note",
      +  "Call",
      +  "ThreadedReply"
      +]
    • changedInput schema / required
      Previous value: -[
      -  "refType",
      -  "refId",
      -  "emoji"
      -]New value: +[
      +  "refType",
      +  "refId"
      +]
  2. First observedv1.1.1

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare write, non-idempotent, non-destructive, closed-world. The description adds meaningful context beyond them: reactions are recorded under the API key owner's identity, and the endpoint is beta. It stops short of saying whether a duplicate reaction errors, overwrites, or is silently ignored — a real gap given idempotentHint=false.

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 front-loaded sentence with the resource and valid targets up front, followed by the ownership and beta qualifiers. No wasted words; only the abrupt 'Beta endpoint.' fragment slightly weakens the prose.

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?

With only three simple parameters and annotations covering the safety profile, most essentials are present. However, there is no output schema and the description never indicates what the call returns (e.g. the created reaction ID or object), nor how duplicate reactions behave — details an agent would want before invoking a non-idempotent write.

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%, with body, refId, and an enum-constrained refType all documented in the schema. The description restates the target types but adds no formatting, length, or default guidance beyond what structured fields provide, so baseline 3 applies.

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

Purpose5/5

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

States a specific verb and resource ('Add an emoji reaction') and enumerates the exact target types (Note, Call, ThreadedReply). The 'as the API key owner' clause and the beta marker give an agent a precise mental model of what gets created and under whose identity.

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 when-to-use or when-not-to-use guidance, and no mention of the sibling getReactions for reading existing reactions. 'Beta endpoint' is a stability caveat, not usage guidance, so the agent gets no routing help.

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