Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

createTextMessage

Log an already-sent SMS message to a Follow Up Boss contact timeline without sending it; requires registered system credentials and sender/recipient details.

Instructions

LOG a text already sent by a registered SMS system; it does not send anything. Needs X-System credentials. personId, message, toNumber, fromNumber are all required.

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": {
      "personId": "<personId>",
      "message": "<message>",
      "toNumber": "<toNumber>",
      "fromNumber": "<fromNumber>"
    },
    "name": "createTextMessage"
  }
}

Input Schema

NameRequiredDescriptionDefault
messageYesMessage body.
personIdYesPerson ID.
toNumberYesRecipient number.
fromNumberYesSender number.
isIncomingNotrue = from the person. Default false.
externalUrlNoLink shown in the timeline byline.
externalLabelNoByline text on the timeline.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv2.0.0
    • changedInput schema / properties / externalLabel / description
      Previous value: -"Label shown to the user (e.g. 'My SMS App')"New value: +"Byline text on the timeline."
    • changedInput schema / properties / externalUrl / description
      Previous value: -"Link to view the original message in your system"New value: +"Link shown in the timeline byline."
    • changedInput schema / properties / fromNumber / description
      Previous value: -"Sender phone number"New value: +"Sender number."
    • changedInput schema / properties / isIncoming / description
      Previous value: -"true = inbound to your user; default false"New value: +"true = from the person. Default false."
    • changedInput schema / properties / message / description
      Previous value: -"Message body"New value: +"Message body."
    • changedInput schema / properties / personId / description
      Previous value: -"Person ID"New value: +"Person ID."
    • changedInput schema / properties / personId / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / toNumber / description
      Previous value: -"Recipient phone number"New value: +"Recipient number."
    • changedInput schema / required
      Previous value: -[
      -  "personId",
      -  "message"
      -]New value: +[
      +  "personId",
      +  "message",
      +  "toNumber",
      +  "fromNumber"
      +]
  2. Changed7 schema fields changedv1.1.3
    • addedInput schema / properties / externalLabel
      Added value: +{
      +  "description": "Label shown to the user (e.g. 'My SMS App')",
      +  "type": "string"
      +}
    • addedInput schema / properties / externalUrl
      Added value: +{
      +  "description": "Link to view the original message in your system",
      +  "type": "string"
      +}
    • addedInput schema / properties / fromNumber
      Added value: +{
      +  "description": "Sender phone number",
      +  "type": "string"
      +}
    • addedInput schema / properties / isIncoming
      Added value: +{
      +  "description": "true = inbound to your user; default false",
      +  "type": "boolean"
      +}
    • changedInput schema / properties / message / description
      Previous value: -"Message text"New value: +"Message body"
    • addedInput schema / properties / toNumber
      Added value: +{
      +  "description": "Recipient phone number",
      +  "type": "string"
      +}
    • removedInput schema / properties / userId
      Removed value: -{
      -  "description": "Sending user ID",
      -  "type": "number"
      -}
  3. First observedv1.1.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already state readOnlyHint=false and destructiveHint=false, so the write-but-not-destructive profile is covered. The description adds genuinely non-structured context: the operation performs no sending, and it requires X-System credentials — an auth precondition an agent cannot infer from the schema or annotations.

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?

Three short clauses, front-loaded with the core clarification (log, not send) before the auth prerequisite and required-field summary. Nothing is restated or padded.

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 7-parameter mutation with no output schema, the description covers purpose, the critical non-sending behavior, auth requirements, and required fields. Remaining details are fully handled by the rich schema, though return/response shape is left unmentioned.

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 seven parameters including isIncoming, externalUrl, and externalLabel are documented in the schema itself. The description merely re-lists the four required names without adding format, constraint, or semantics beyond the schema, which is the baseline case.

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?

Names a specific verb and resource ('LOG a text already sent') and immediately disambiguates from a send operation ('it does not send anything'). This is decisive against siblings like createTextMessageTemplate or inboxAppAddMessage, which an agent could otherwise confuse with it.

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?

The condition for use is clear: only for messages already sent by a registered SMS system, i.e. a logging/backfill path rather than an outbound path. It stops short of naming an alternative tool for actually sending, so it is clear context without explicit exclusion routing.

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