save_playbook

Save the playbook

Act · mcp:actIdempotent

Saves the go-to-market playbook: the messaging angles, the cadence — three emails, sent on days 0, 3 and 7 — and the number of meetings a month the user aims at.

Description the model readsSent as is in tools/list.

Save the go-to-market playbook: the messaging angles, the cadence and the number of meetings a month the user wants to aim at. That number is their objective: nothing here forecasts it.

Example

The user says

I'd like about 8 meetings a month. Push the missed-calls angle.

tools/call · Arguments the assistant sends

{
  "name": "save_playbook",
  "arguments": {
    "angles": [
      "No more missed calls: every patient gets an answer",
      "Your front desk gets two hours a day back"
    ],
    "cadence": "3 emails, sent on day 0, day 3 and day 7",
    "targetMeetingsPerMonth": 8
  }
}

Arguments

anglesstring[]required3–300 chars1–6 items

cadencestringrequired3–400 chars

The cadence, fixed at 3 emails, sent on day 0, day 3, day 7: record it, never another.

targetMeetingsPerMonthintegerrequired1–500

Input schema

{
  "type": "object",
  "properties": {
    "angles": {
      "minItems": 1,
      "maxItems": 6,
      "type": "array",
      "items": {
        "type": "string",
        "minLength": 3,
        "maxLength": 300
      }
    },
    "cadence": {
      "type": "string",
      "minLength": 3,
      "maxLength": 400,
      "description": "The cadence, fixed at 3 emails, sent on day 0, day 3, day 7: record it, never another."
    },
    "targetMeetingsPerMonth": {
      "type": "integer",
      "minimum": 1,
      "maximum": 500
    }
  },
  "required": ["angles", "cadence", "targetMeetingsPerMonth"]
}

Result

Result kindplaybook

kind"playbook"

playbookobject

• angles string[]
• cadence string
• targetMeetingsPerMonth integer

appUrlstring

Output schema

{
  "type": "object",
  "properties": {
    "kind": {
      "type": "string",
      "const": "playbook"
    },
    "playbook": {
      "type": "object",
      "properties": {
        "angles": {
          "type": "array",
          "items": {
            "type": "string"
          }
        },
        "cadence": {
          "type": "string"
        },
        "targetMeetingsPerMonth": {
          "type": "integer"
        }
      },
      "required": ["angles", "cadence", "targetMeetingsPerMonth"],
      "additionalProperties": false
    },
    "appUrl": {
      "type": "string"
    }
  },
  "required": ["kind", "playbook", "appUrl"],
  "additionalProperties": false
}

Good to know

• The number of meetings is the user's objective: VibeSell forecasts nothing from it.

Related tools

save_offerSave the offer

estimate_campaign_planEstimate a campaign