Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

createDeal

Creates a Follow Up Boss deal with required name and stage, plus optional price, people, dates, and custom fields for CRM pipeline tracking.

Instructions

Create a deal. name and stageId are required. Use peopleIds (array) and price (whole number); do not use personId or 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": {
      "name": "<name>",
      "stageId": "<stageId>"
    },
    "name": "createDeal"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesName of the deal.
priceNoPrice associated with the deal (whole number).
stageIdYesStage the deal is assigned to.
userIdsNoUser IDs to include in the deal.
peopleIdsNoPerson IDs to include in the deal.
descriptionNoDescription of the deal.
orderWeightNoSets a specific sort order.
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. Changed31 schema fields changedv2.0.0
    • addedInput schema / additionalProperties
      Added value: +true
    • addedInput schema / properties / agentCommission / description
      Added value: +"Commission split for the agent."
    • changedInput schema / properties / agentCommission / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / properties / commissionValue / description
      Added value: +"Commission value for the deal."
    • changedInput schema / properties / commissionValue / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / description / description
      Previous value: -"Deal description"New value: +"Description of the deal."
    • addedInput schema / properties / dueDiligenceDate / description
      Added value: +"Due diligence date, YYYY-MM-DD."
    • addedInput schema / properties / dueDiligenceDate / format
      Added value: +"date"
    • addedInput schema / properties / earnestMoneyDueDate / description
      Added value: +"Earnest money due date, YYYY-MM-DD."
    • addedInput schema / properties / earnestMoneyDueDate / format
      Added value: +"date"
    • addedInput schema / properties / finalWalkThroughDate / description
      Added value: +"Final walk-through date, YYYY-MM-DD."
    • addedInput schema / properties / finalWalkThroughDate / format
      Added value: +"date"
    • addedInput schema / properties / mutualAcceptanceDate / description
      Added value: +"Mutual acceptance date, YYYY-MM-DD."
    • addedInput schema / properties / mutualAcceptanceDate / format
      Added value: +"date"
    • changedInput schema / properties / name / description
      Previous value: -"Deal name"New value: +"Name of the deal."
    • changedInput schema / properties / orderWeight / description
      Previous value: -"Sort order weight"New value: +"Sets a specific sort order."
    • changedInput schema / properties / orderWeight / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / peopleIds / description
      Previous value: -"Person IDs on the deal"New value: +"Person IDs to include in the deal."
    • changedInput schema / properties / peopleIds / items / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / properties / possessionDate / description
      Added value: +"Possession date, YYYY-MM-DD."
    • addedInput schema / properties / possessionDate / format
      Added value: +"date"
    • changedInput schema / properties / price / description
      Previous value: -"Deal 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"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 (required)"New value: +"Stage the deal is assigned to."
    • changedInput schema / properties / stageId / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / properties / teamCommission / description
      Added value: +"Commission split for the team."
    • changedInput schema / properties / teamCommission / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / userIds / description
      Previous value: -"Assigned user IDs"New value: +"User IDs to include in the deal."
    • changedInput schema / properties / userIds / items / type
      Previous value: -"number"New value: +"integer"
  2. Changed18 schema fields changedv1.1.3
    • addedInput schema / properties / agentCommission
      Added value: +{
      +  "type": "number"
      +}
    • removedInput schema / properties / closingDate
      Removed value: -{
      -  "description": "Closing date ISO",
      -  "type": "string"
      -}
    • addedInput schema / properties / commissionValue
      Added value: +{
      +  "type": "number"
      +}
    • addedInput schema / properties / description
      Added value: +{
      +  "description": "Deal description",
      +  "type": "string"
      +}
    • addedInput schema / properties / dueDiligenceDate
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / earnestMoneyDueDate
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / finalWalkThroughDate
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / mutualAcceptanceDate
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / peopleIds
      Added value: +{
      +  "description": "Person IDs on the 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 / possessionDate
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / price
      Added value: +{
      +  "description": "Deal price",
      +  "type": "number"
      +}
    • addedInput schema / properties / projectedCloseDate
      Added value: +{
      +  "description": "Projected close date",
      +  "type": "string"
      +}
    • changedInput schema / properties / stageId / description
      Previous value: -"Stage ID"New value: +"Stage ID (required)"
    • addedInput schema / properties / teamCommission
      Added value: +{
      +  "type": "number"
      +}
    • removedInput schema / properties / value
      Removed value: -{
      -  "description": "Deal value",
      -  "type": "number"
      -}
    • changedInput schema / required
      Previous value: -[]New value: +[
      +  "name",
      +  "stageId"
      +]
  3. First observedv1.1.1

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare a non-read-only, non-destructive, non-idempotent write, and the description does not repeat that. It does add real behavioral detail by disclosing that arbitrary custom field values are accepted as extra properties, a trait not visible from the enumerated schema. It says nothing about permissions, whether duplicate deals are allowed (relevant given idempotentHint=false), or what happens when stageId is invalid.

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 sentences, front-loaded with the required fields before the name-correction guidance and the custom-field note. No filler, no restatement of the tool name.

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 creation tool with fully documented schema and safety annotations, the description covers the essentials and closes the main semantic trap. The one gap is that with no output schema, the agent cannot tell what a successful create returns (e.g. the new deal's ID), which matters for chaining calls.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3, but the description goes beyond it by resolving the peopleIds/personId and price/value naming ambiguities and by explaining the additionalProperties escape hatch for custom fields. Those are meaningful semantics the schema alone cannot convey. The remaining 14 optional fields (commissions, dates) get no extra guidance, keeping it from a 5.

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?

Opens with a specific verb+resource ("Create a deal") and immediately names the two required fields, so the agent knows exactly what the tool produces. It does not distinguish this from sibling creators like createDealCustomField or createDealAttachment, but the distinction is largely self-evident from the names.

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?

Offers concrete negative guidance ("do not use personId or value") and ties peopleIds/price to their correct forms, which steers invocation. It gives no when-to-use-vs-alternative framing, e.g. that updateDeal should be used for existing deals, so usage context is only implied.

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