Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

createCall

Log an inbound or outbound call on a person in Follow Up Boss, capturing required person ID, phone, direction, and optional outcome, duration, and notes.

Instructions

Log a call on a person. personId, phone, and isIncoming are required. userId can only be set by administrators (defaults to API user).

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>",
      "phone": "<phone>",
      "isIncoming": "<isIncoming>"
    },
    "name": "createCall"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNoCall log message.
phoneYesPhone number on the call.
userIdNoUser who took the call; admin only.
outcomeNoCall outcome.
durationNoSeconds.
personIdYesPerson ID.
toNumberNoNumber called.
fromNumberNoNumber called from.
isIncomingYestrue = incoming, false = outgoing.
recordingUrlNoURL of the call recording.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed15 schema fields changedv2.0.0
    • changedInput schema / properties / duration / description
      Previous value: -"Call duration in seconds"New value: +"Seconds."
    • changedInput schema / properties / duration / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / fromNumber / description
      Previous value: -"Originating number"New value: +"Number called from."
    • changedInput schema / properties / isIncoming / description
      Previous value: -"true = inbound, false = outbound"New value: +"true = incoming, false = outgoing."
    • changedInput schema / properties / note / description
      Previous value: -"Call note"New value: +"Call log message."
    • changedInput schema / properties / outcome / description
      Previous value: -"Call outcome"New value: +"Call outcome."
    • addedInput schema / properties / outcome / enum
      Added value: +[
      +  "Interested",
      +  "Not Interested",
      +  "Left Message",
      +  "No Answer",
      +  "Busy",
      +  "Bad Number"
      +]
    • 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 / phone / description
      Previous value: -"Phone number on the call"New value: +"Phone number on the call."
    • addedInput schema / properties / recordingUrl
      Added value: +{
      +  "description": "URL of the call recording.",
      +  "type": "string"
      +}
    • changedInput schema / properties / toNumber / description
      Previous value: -"Destination number"New value: +"Number called."
    • changedInput schema / properties / userId / description
      Previous value: -"User who made the call"New value: +"User who took the call; admin only."
    • changedInput schema / properties / userId / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / required
      Previous value: -[
      -  "personId"
      -]New value: +[
      +  "personId",
      +  "phone",
      +  "isIncoming"
      +]
  2. Changed1 schema field changedv1.4.3
    • removedInput schema / properties / recordingUrl
      Removed value: -{
      -  "description": "Recording URL",
      -  "type": "string"
      -}
  3. Changed10 schema fields changedv1.1.3
    • removedInput schema / properties / direction
      Removed value: -{
      -  "description": "Call direction: inbound or outbound",
      -  "type": "string"
      -}
    • addedInput schema / properties / fromNumber
      Added value: +{
      +  "description": "Originating number",
      +  "type": "string"
      +}
    • addedInput schema / properties / isIncoming
      Added value: +{
      +  "description": "true = inbound, false = outbound",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / note
      Added value: +{
      +  "description": "Call note",
      +  "type": "string"
      +}
    • removedInput schema / properties / notes
      Removed value: -{
      -  "description": "Call notes",
      -  "type": "string"
      -}
    • removedInput schema / properties / occurredAt
      Removed value: -{
      -  "description": "ISO timestamp when call occurred",
      -  "type": "string"
      -}
    • addedInput schema / properties / outcome
      Added value: +{
      +  "description": "Call outcome",
      +  "type": "string"
      +}
    • addedInput schema / properties / phone
      Added value: +{
      +  "description": "Phone number on the call",
      +  "type": "string"
      +}
    • addedInput schema / properties / recordingUrl
      Added value: +{
      +  "description": "Recording URL",
      +  "type": "string"
      +}
    • addedInput schema / properties / toNumber
      Added value: +{
      +  "description": "Destination number",
      +  "type": "string"
      +}
  4. First observedv1.1.1

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false, and openWorldHint=false, so safety profile is covered. The description adds one genuinely new behavioral fact — userId defaults to the API user and is admin-only — but says nothing about duplicate risk on retry (non-idempotent) or side effects such as activity-feed entries.

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 short sentences, front-loaded with the action and then the constraints, with no filler. The middle sentence repeating the schema's required list is slightly wasteful but harmless.

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 10-parameter mutation tool with no output schema, the definition covers the action, required fields, and the admin restriction, which is enough to call it correctly. It leaves open what the response contains and how optional fields like duration, outcome, and recordingUrl interact with the log entry.

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 every one of the 10 parameters is already documented in the schema. The description restates the three required fields (redundant with `required`) and contributes one extra detail: the default value and permission gate for userId. Baseline 3 is appropriate.

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 opens with a specific verb and resource ("Log a call on a person"), which clearly separates it from siblings such as createNote, createTextMessage, or updateCall. It stops short of naming an alternative tool or stating scope limits, so it is clear but not fully differentiated.

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

Usage Guidelines3/5

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

Usage is only implied by the verb "log" — an agent can infer this is for recording a completed or in-progress call. There is no explicit guidance on when to prefer createCall over updateCall, createNote, or createAppointment, and no stated exclusions.

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