Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

updateDeal

DestructiveIdempotent

Update a deal by ID, sending only fields to change; peopleIds and userIds replace full lists, and custom fields can be passed as extra properties.

Instructions

Update a deal by ID; send only fields to change. peopleIds and userIds replace the full list. Use peopleIds (not personId) and price (not value). Custom field values may be passed as extra properties (e.g. customField1).

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

Input Schema

NameRequiredDescriptionDefault
idYesDeal ID.
nameNoName of the deal.
priceNoPrice associated with the deal (whole number).
stageIdNoStage the deal is assigned to.
userIdsNoUser IDs to include in the deal.
peopleIdsNoPerson IDs to include in the deal.
descriptionNoDescription of the deal.
possessionDateNoPossession date, YYYY-MM-DD.
teamCommissionNoCommission split for the team.
agentCommissionNoCommission split for the agent.
commissionValueNoCommission value for the deal.
dueDiligenceDateNoDue diligence date, YYYY-MM-DD.
projectedCloseDateNoProjected close date, YYYY-MM-DD.
earnestMoneyDueDateNoEarnest money due date, YYYY-MM-DD.
finalWalkThroughDateNoFinal walk-through date, YYYY-MM-DD.
mutualAcceptanceDateNoMutual acceptance date, YYYY-MM-DD.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed28 schema fields changedv2.0.0
    • addedInput schema / additionalProperties
      Added value: +true
    • changedInput schema / properties / agentCommission / description
      Previous value: -"Agent commission split"New value: +"Commission split for the agent."
    • changedInput schema / properties / commissionValue / description
      Previous value: -"Total commission value"New value: +"Commission value for the deal."
    • changedInput schema / properties / description / description
      Previous value: -"Description"New value: +"Description of the deal."
    • changedInput schema / properties / dueDiligenceDate / description
      Previous value: -"Due diligence date (YYYY-MM-DD)"New value: +"Due diligence date, YYYY-MM-DD."
    • addedInput schema / properties / dueDiligenceDate / format
      Added value: +"date"
    • changedInput schema / properties / earnestMoneyDueDate / description
      Previous value: -"Earnest money due date (YYYY-MM-DD)"New value: +"Earnest money due date, YYYY-MM-DD."
    • addedInput schema / properties / earnestMoneyDueDate / format
      Added value: +"date"
    • changedInput schema / properties / finalWalkThroughDate / description
      Previous value: -"Final walk-through date (YYYY-MM-DD)"New value: +"Final walk-through date, YYYY-MM-DD."
    • addedInput schema / properties / finalWalkThroughDate / format
      Added value: +"date"
    • changedInput schema / properties / id / description
      Previous value: -"Deal ID"New value: +"Deal ID."
    • changedInput schema / properties / id / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / mutualAcceptanceDate / description
      Previous value: -"Mutual acceptance date (YYYY-MM-DD)"New value: +"Mutual acceptance date, YYYY-MM-DD."
    • addedInput schema / properties / mutualAcceptanceDate / format
      Added value: +"date"
    • changedInput schema / properties / name / description
      Previous value: -"Name"New value: +"Name of the deal."
    • changedInput schema / properties / peopleIds / description
      Previous value: -"People on deal"New value: +"Person IDs to include in the deal."
    • changedInput schema / properties / peopleIds / items / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / possessionDate / description
      Previous value: -"Possession date (YYYY-MM-DD)"New value: +"Possession date, YYYY-MM-DD."
    • addedInput schema / properties / possessionDate / format
      Added value: +"date"
    • changedInput schema / properties / price / description
      Previous value: -"Price"New value: +"Price associated with the deal (whole number)."
    • changedInput schema / properties / price / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / projectedCloseDate / description
      Previous value: -"Projected close date (YYYY-MM-DD)"New value: +"Projected close date, YYYY-MM-DD."
    • addedInput schema / properties / projectedCloseDate / format
      Added value: +"date"
    • changedInput schema / properties / stageId / description
      Previous value: -"Stage ID"New value: +"Stage the deal is assigned to."
    • changedInput schema / properties / stageId / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / teamCommission / description
      Previous value: -"Team commission split"New value: +"Commission split for the team."
    • changedInput schema / properties / userIds / description
      Previous value: -"User IDs"New value: +"User IDs to include in the deal."
    • changedInput schema / properties / userIds / items / type
      Previous value: -"number"New value: +"integer"
  2. Changed9 schema fields changedv1.1.4
    • addedInput schema / properties / agentCommission
      Added value: +{
      +  "description": "Agent commission split",
      +  "type": "integer"
      +}
    • addedInput schema / properties / commissionValue
      Added value: +{
      +  "description": "Total commission value",
      +  "type": "integer"
      +}
    • addedInput schema / properties / dueDiligenceDate
      Added value: +{
      +  "description": "Due diligence date (YYYY-MM-DD)",
      +  "type": "string"
      +}
    • addedInput schema / properties / earnestMoneyDueDate
      Added value: +{
      +  "description": "Earnest money due date (YYYY-MM-DD)",
      +  "type": "string"
      +}
    • addedInput schema / properties / finalWalkThroughDate
      Added value: +{
      +  "description": "Final walk-through date (YYYY-MM-DD)",
      +  "type": "string"
      +}
    • addedInput schema / properties / mutualAcceptanceDate
      Added value: +{
      +  "description": "Mutual acceptance date (YYYY-MM-DD)",
      +  "type": "string"
      +}
    • addedInput schema / properties / possessionDate
      Added value: +{
      +  "description": "Possession date (YYYY-MM-DD)",
      +  "type": "string"
      +}
    • addedInput schema / properties / projectedCloseDate
      Added value: +{
      +  "description": "Projected close date (YYYY-MM-DD)",
      +  "type": "string"
      +}
    • addedInput schema / properties / teamCommission
      Added value: +{
      +  "description": "Team commission split",
      +  "type": "integer"
      +}
  3. Changed5 schema fields changedv1.1.3
    • addedInput schema / properties / peopleIds
      Added value: +{
      +  "description": "People on deal",
      +  "items": {
      +    "type": "number"
      +  },
      +  "type": "array"
      +}
    • removedInput schema / properties / personId
      Removed value: -{
      -  "description": "Person ID",
      -  "type": "number"
      -}
    • removedInput schema / properties / pipelineId
      Removed value: -{
      -  "description": "Pipeline ID",
      -  "type": "number"
      -}
    • addedInput schema / properties / price
      Added value: +{
      +  "description": "Price",
      +  "type": "number"
      +}
    • removedInput schema / properties / value
      Removed value: -{
      -  "description": "Value",
      -  "type": "number"
      -}
  4. First observedv1.1.1

TDQS

A4.1/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 repeatable. The description adds one genuinely useful behavioral fact beyond them: peopleIds and userIds replace the entire list rather than appending, which is exactly the kind of destructive nuance an agent needs. It says nothing about failure modes or what happens to omitted fields, so it is good but not rich.

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, front-loaded sentences with no filler; the partial-update rule comes first, then the destructive replacement caveat, then the naming/custom-field rules. Every clause adds actionable information.

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 16-parameter mutation with no output schema, the description covers the essentials: partial updates, list replacement, alias pitfalls, and custom-field passthrough. It could still say what happens to unsent fields or an unknown ID, but nothing critical to invoking it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, and the description earns more by adding meaning the schema does not carry: list-replacement semantics for peopleIds/userIds, canonical field names (peopleIds over personId, price over value), and the fact that custom fields go in as extra properties like customField1, which explains the schema's additionalProperties: true.

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, 'Update a deal by ID', and immediately scopes the operation as a partial update ('send only fields to change'). It is clearly distinguishable from createDeal/getDeal in intent, though it never names a sibling tool explicitly.

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?

It gives concrete when-to-use guidance ('send only fields to change', use peopleIds not personId, price not value) that steers the agent away from common mistakes. It stops short of naming alternatives or stating prerequisites/exclusions in terms of other tools.

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