Update call record details in Follow Up Boss CRM, including notes, outcomes, duration, and caller info.
Update a call record
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Call ID | |
| note | No | Note | |
| phone | No | Phone number | |
| userId | No | User ID | |
| outcome | No | Outcome | |
| duration | No | Duration | |
| personId | No | Person ID | |
| toNumber | No | ||
| fromNumber | No | ||
| isIncoming | No | true = inbound |
Changes observed during successful MCP inspections.
v1.4.3Input schema / properties / recordingUrlRemoved value: -{
- "type": "string"
-}v1.1.3Input schema / properties / directionRemoved value: -{
- "description": "Direction",
- "type": "string"
-}Input schema / properties / fromNumberAdded value: +{
+ "type": "string"
+}Input schema / properties / isIncomingAdded value: +{
+ "description": "true = inbound",
+ "type": "boolean"
+}Input schema / properties / noteAdded value: +{
+ "description": "Note",
+ "type": "string"
+}Input schema / properties / notesRemoved value: -{
- "description": "Notes",
- "type": "string"
-}Input schema / properties / occurredAtRemoved value: -{
- "description": "Timestamp",
- "type": "string"
-}Input schema / properties / outcomeAdded value: +{
+ "description": "Outcome",
+ "type": "string"
+}Input schema / properties / phoneAdded value: +{
+ "description": "Phone number",
+ "type": "string"
+}Input schema / properties / recordingUrlAdded value: +{
+ "type": "string"
+}Input schema / properties / toNumberAdded value: +{
+ "type": "string"
+}v1.1.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description bears full burden. It only states 'update' which implies mutation, but does not disclose side effects, permissions, idempotency, or error behavior. For a mutation tool, this is insufficient.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence, which is concise but lacks structure or additional context. It is minimally acceptable but not exemplary.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's complexity (10 parameters, no output schema, no annotations), the description is too sparse. It does not explain return values, behavior, or constraints, leaving significant gaps.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 80%, so the schema already documents most parameters. The description adds no meaning beyond the schema, meeting the baseline score of 3.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description 'Update a call record' clearly states the verb (update) and resource (call record). It is specific enough to identify the tool's function, though it does not explicitly distinguish it from sibling tools like createCall or getCall.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives, such as when a call exists or what prerequisites are needed. The description lacks context for appropriate usage.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.