Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

updateCall

DestructiveIdempotent

Modify an existing call record's outcome, note, duration, or phone details. Update call logs only when the call was created by the same API account.

Instructions

Update a call record. Only calls created by the same API system/account can be updated.

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

Input Schema

NameRequiredDescriptionDefault
idYesCall ID.
noteNoCall log message.
phoneNoPhone number.
userIdNoUser ID; admin only.
outcomeNoCall outcome.
durationNoSeconds.
personIdNoPerson ID.
toNumberNoNumber called.
fromNumberNoNumber called from.
isIncomingNotrue = incoming.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed15 schema fields changedv2.0.0
    • changedInput schema / properties / duration / description
      Previous value: -"Duration"New value: +"Seconds."
    • changedInput schema / properties / duration / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / properties / fromNumber / description
      Added value: +"Number called from."
    • changedInput schema / properties / id / description
      Previous value: -"Call ID"New value: +"Call ID."
    • changedInput schema / properties / id / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / isIncoming / description
      Previous value: -"true = inbound"New value: +"true = incoming."
    • changedInput schema / properties / note / description
      Previous value: -"Note"New value: +"Call log message."
    • changedInput schema / properties / outcome / description
      Previous value: -"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"New value: +"Phone number."
    • addedInput schema / properties / toNumber / description
      Added value: +"Number called."
    • changedInput schema / properties / userId / description
      Previous value: -"User ID"New value: +"User ID; admin only."
    • changedInput schema / properties / userId / type
      Previous value: -"number"New value: +"integer"
  2. Changed1 schema field changedv1.4.3
    • removedInput schema / properties / recordingUrl
      Removed value: -{
      -  "type": "string"
      -}
  3. Changed10 schema fields changedv1.1.3
    • removedInput schema / properties / direction
      Removed value: -{
      -  "description": "Direction",
      -  "type": "string"
      -}
    • addedInput schema / properties / fromNumber
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / isIncoming
      Added value: +{
      +  "description": "true = inbound",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / note
      Added value: +{
      +  "description": "Note",
      +  "type": "string"
      +}
    • removedInput schema / properties / notes
      Removed value: -{
      -  "description": "Notes",
      -  "type": "string"
      -}
    • removedInput schema / properties / occurredAt
      Removed value: -{
      -  "description": "Timestamp",
      -  "type": "string"
      -}
    • addedInput schema / properties / outcome
      Added value: +{
      +  "description": "Outcome",
      +  "type": "string"
      +}
    • addedInput schema / properties / phone
      Added value: +{
      +  "description": "Phone number",
      +  "type": "string"
      +}
    • addedInput schema / properties / recordingUrl
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / toNumber
      Added value: +{
      +  "type": "string"
      +}
  4. First observedv1.1.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the agent knows this mutates and is repeat-safe. The description adds a genuinely useful ownership/scope constraint not present in annotations, but it never clarifies whether omitted fields are left unchanged or cleared, which matters for a destructive 10-field update.

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, front-loaded with the action and immediately followed by the constraint. Nothing is redundant or buried.

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 description plus complete schema and annotations cover the essentials. The missing piece is update semantics — partial vs full replacement — which an agent would want before calling with only the required 'id'.

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 every parameter including the enum-constrained outcome documented inline. The description adds no parameter-level meaning beyond the schema, so the baseline of 3 applies.

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+resource ('Update a call record'), which cleanly separates it from createCall/getCall/listCalls in the sibling list. It does not enumerate what fields are updatable, but the resource 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 Guidelines3/5

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

Adds one real gating rule ('Only calls created by the same API system/account can be updated'), which tells the agent a precondition for use. It gives no explicit guidance on when to prefer getCall first, or how this relates to createCall, so usage is implied rather than spelled out.

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