← Files Follow Up BossARCHIVED FILE

plugin.json

19.5 KB · Nov 18, 2026 · 06:19 UTC

↓ Download file

{
  "$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
  "author": {
    "email": "petery@zillowgroup.com",
    "name": "Peter Yao",
    "url": "https://www.followupboss.com/"
  },
  "description": "Use the production Follow Up Boss MCP with skills for tool discovery, follow-up, reviewed CRM changes, and reporting.",
  "extensions": {
    "com.openai": {
      "interface": {
        "capabilities": [
          "Find contacts and review recent notes",
          "Review tasks, appointments, and smart lists",
          "Prepare SMS and email drafts",
          "Review supported CRM updates"
        ],
        "category": "Business & Operations",
        "composerIcon": "./assets/icon.png",
        "defaultPrompt": [
          "What Follow Up Boss tasks do I have due today?",
          "Show my Follow Up Boss smart lists.",
          "Show up to five contacts created in the past 24 hours."
        ],
        "developerName": "Peter Yao",
        "displayName": "Follow Up Boss",
        "logo": "./assets/icon.png",
        "longDescription": "Follow Up Boss helps real estate agents and teams work with their CRM in chat. Connect your existing Follow Up Boss account to review contacts and recent notes, plan follow-up from tasks, appointments and smart lists, draft personalized outreach, and analyze agent activity and conversation counts. Prepare supported CRM changes for review and confirm them in the review interface before saving. Email and SMS messages remain drafts; the plugin does not send messages or place calls. Requires Follow Up Boss sign-in and applicable account permissions. Results reflect the records and coverage available to your connected account.",
        "privacyPolicyURL": "https://www.followupboss.com/legal-pages/privacy-notice",
        "shortDescription": "Your real estate CRM assistant",
        "supportURL": "https://help.followupboss.com/hc/en-us/requests/new",
        "termsOfServiceURL": "https://www.followupboss.com/legal-pages/terms-of-service",
        "websiteURL": "https://www.followupboss.com/"
      },
      "publication": {
        "release_notes": "Adds five positive and three negative review cases and the verified demo recording. Reconciles test instructions with existing sample data: current-day brief checks, current latest notes and uniquely named review writes. Preserves the four skills and production MCP connection. Test definitions are not claims of passed execution.",
        "countries": []
      },
      "review": {
        "test_cases": {
          "positive": [
            {
              "description": "P1 \u2014 Authenticated daily planning with current account data\nUse the dedicated sample-data FUB account supplied through secure reviewer credentials, connected to https://fub-mcp.zillow.com/ with the submitted four skills. Start a fresh chat and select Follow Up Boss. Resolve IDs from live tool results. Do not create an account or reset sample records. \nSetup: Use the existing demo account and its FUB timezone. No named QA task or appointment fixtures are required. Today is the execution date in that timezone, not the recording date. Empty sections are valid boundary cases.\nExecution: Run the prompt and compare identity, date, section counts and shown items with the actual tool results. When independently checking in FUB, use the same user, local date, task status and appointment scope. Do not alter records to obtain a nonzero result.\nEvidence scope: The November 6 walkthrough demonstrates current data; the prior version's uncreated named fixtures were not tested. This revision tests returned-data accuracy and coverage, not those missing fixtures.",
              "prompt": "Which Follow Up Boss user am I connected as? Give me my morning brief with today\u2019s appointments, tasks due today, overdue tasks, and any leads needing a response or follow-up. Include my timezone and any coverage limitations.",
              "tools_triggered": "mcp_app_get-current-user; mcp_app_get_my_daily_brief",
              "expected_behavior": "Resolve the authenticated user through mcp_app_get-current-user and call mcp_app_get_my_daily_brief with remainingOnly=false or omitted. State the returned user timezone and execution date. Accurately report today's FUB appointments, tasks due today, overdue tasks, unanswered texts/emails in the returned window, and follow-up leads. Match every count and item to the returned data; distinguish totals from the first five shown. Preserve true zero values and partial/unavailable sections. Do not imply synced Google/Outlook calendar coverage or that a time is free. Convert displayed times using the correct timezone and date offset. No CRM writes. The brief is data-only; a widget is not required. A partial result can satisfy the honesty check but does not establish complete section coverage. Do not hardcode the recording's counts."
            },
            {
              "description": "P2 \u2014 Contact discovery, disambiguation and latest notes\nUse the dedicated sample-data FUB account supplied through secure reviewer credentials, connected to https://fub-mcp.zillow.com/ with the submitted four skills. Start a fresh chat and select Follow Up Boss. Resolve IDs from live tool results. Do not create an account or reset sample records. \nExisting fixtures: Two contacts named FUB Review Buyer, distinguished by buyer.a@example.com and buyer.b@example.com. These synthetic addresses must never be messaged. Buyer A has sample notes; do not reset or delete notes from prior runs.\nExecution: Run the prompt, then answer the clarification with: \"Use the contact with email buyer.a@example.com.\" Compare the selected contact's latest two returned notes with its current FUB record. Run before P4 for a stable within-run baseline.\nReference snapshot: After the November 6 recording, A's latest notes were 12 (QA GPT demo follow-up 2026-11-06) and 11 (QA consultation follow-up). Subsequent authorized tests may add newer notes; judge ordering/content against the live record rather than these historical IDs.\nEvidence scope: The recording predates note 12 and showed notes 11 and 8. Its initial UTC-as-Pacific prose error required a correction; that is not a clean timezone pass.",
              "prompt": "Find FUB Review Buyer in Follow Up Boss and show the latest two notes. If more than one person matches, let me choose before opening the notes.",
              "tools_triggered": "mcp_app_query_people or mcp_app_find_contact; mcp_app_list_notes",
              "expected_behavior": "Present both matching contacts and wait for selection before reading either contact's notes. After selection, call mcp_app_list_notes(personId=<authoritative ID for buyer.a@example.com>, limit=2). Show only the selected contact's current two newest notes in the notes view; match contents, ordering, author and timestamps to the returned records. Use accurate timezone labels and conversions if times are restated. Do not include Buyer B's notes or infer full-history coverage from a bounded read. No writes. Both disambiguation and note rendering must succeed; Unknown tool, Unknown resource or Could not open card fails the UI check. A corrective follow-up must be recorded as recovery, not an initial-response pass."
            },
            {
              "description": "P3 \u2014 Personalized outreach drafts\nUse the dedicated sample-data FUB account supplied through secure reviewer credentials, connected to https://fub-mcp.zillow.com/ with the submitted four skills. Start a fresh chat and select Follow Up Boss. Resolve IDs from live tool results. Do not create an account or reset sample records. \nExisting fixtures: buyer.a@example.com and FUB Review Seller (seller@example.com) carry the tag FUB Plugin Review; buyer.b@example.com is untagged. Buyer notes describe a buyer consultation, weekend tours and checklist follow-up. Seller notes describe selling in spring and a pricing consultation. Use the notes actually returned; sample addresses must never receive messages.\nExecution: Run the prompt, inspect the tagged cohort and both final personalized email cards, and verify each recipient and body. Do not activate Save draft or send controls. Record any extra prompt needed to inspect a card as an adaptation.\nEvidence scope: Both personalized cards were inspected in the recording; an extra inspection prompt was needed for the Buyer card. No message or saved draft was created.",
              "prompt": "Find up to three Follow Up Boss contacts tagged FUB Plugin Review and draft a personalized email for each to schedule a consultation. Use their recent notes and keep everything as drafts for me to review.",
              "tools_triggered": "mcp_app_query_people; mcp_app_draft_outreach_messages; mcp_app_send_message separately for each contact whose starter draft needs personalization",
              "expected_behavior": "Return two final personalized drafts, one for each tagged fixture, and none for untagged B. Buyer text reflects the buyer consultation/weekend context; seller text reflects a pricing consultation. No invented appointments, property matches or message history. Clearly label drafts. No message send, saved-draft write, note/task creation or claim of delivery. Preserve any unavailable-history warning.\nArgument checks: query_people(tags=[\"FUB Plugin Review\"], limit=3), then draft_outreach_messages(personIds=<only returned tagged IDs>, channel=\"email\", goal=\"Schedule a consultation\"). Inspect every batch draft against its own returned notes and history. If a draft is only a starter template, compose a grounded subject/body and call send_message separately for that contact with its authoritative personId, channel=\"email\", subject and body; do this for every contact that needs personalization. Do not activate Save draft or call an apply tool. Both final personalized draft cards must load with the correct contact and recipient, and their subjects/bodies must be verified; preparing only one personalized card does not pass. Wording may vary; factual claims must be supported by the returned notes and history."
            },
            {
              "description": "P4 \u2014 Review, confirm and verify an additive CRM update\nUse the dedicated sample-data FUB account supplied through secure reviewer credentials, connected to https://fub-mcp.zillow.com/ with the submitted four skills. Start a fresh chat and select Follow Up Boss. Resolve IDs from live tool results. Do not create an account or reset sample records. \nExisting fixture: buyer.a@example.com with notes/task write access. Preserve existing sample notes and tasks. Choose a unique run suffix from the current UTC timestamp, show it in both proposed titles, and check recent notes plus current open/completed tasks for a collision before proposing changes. If a collision is found, choose another suffix. This check is bounded for notes, not proof about all historical/deleted records.\nExecution: Run the prompt and record the exact chosen titles, body, owner, contact ID and explicit due time. Inspect the review and unchanged records before confirmation. The authorized reviewer clicks the widget confirmation once, then asks: \"Verify the new note and task were saved on that contact, and show their record IDs, task owner, and due time.\" Compare the readback to the baseline. Do not reset records or replay an uncertain write.\nEvidence scope: The recording saved note 12 and task 7 under distinct November 6 demo titles. The confirmation click occurred off camera; saved receipt and independent readback were verified. Those historical records do not count as execution of this revised case.",
              "prompt": "For the Follow Up Boss contact with email buyer.a@example.com, prepare a note with the text \"Demo review only: buyer requested the preparation checklist before our consultation.\" and a task assigned to me, due tomorrow at 10:00 AM in my FUB timezone. Use \"QA review follow-up\" as the note title and \"QA review buyer checklist\" as the task title, appending the same unique timestamp suffix to both so this run is distinguishable from earlier tests. Check for matching existing records first. Show the exact titles and let me review both changes before saving.",
              "tools_triggered": "mcp_app_get-current-user; mcp_app_query_people or mcp_app_find_contact; mcp_app_interaction_update; mcp_app_apply_interaction_update (widget only, after human confirmation); mcp_app_list_notes; mcp_app_get_tasks",
              "expected_behavior": "Resolve the authenticated user/timezone and exact contact from authoritative results. Read recent notes and current open/completed contact tasks as the baseline, honoring pagination and coverage. Choose a unique timestamp suffix and show both full titles. Call interaction_update with the exact personId, noteSubject, supplied noteBody, taskDescription, authenticated taskAssignedUserId, explicit tomorrow-at-10:00 local date/time with correct UTC offset, taskTimeZone and a unique taskRequestId. Render a review for exactly one note and one task; no new records may exist before confirmation. Only the authorized reviewer confirms through the widget; apply_interaction_update is widget-only and must never be invoked from chat. Do not expose proposal/confirmation secrets. After confirmation, show the actual receipt and independently read back newly returned note/task IDs, exact titles/body, correct contact/owner and due time. Preserve old records. If a proposal expires, get a fresh review; if a write times out or returns partial/uncertain status, inspect persisted state before any retry and do not create duplicates. A review alone is not success. Missing widget or failed readback prevents a pass."
            },
            {
              "description": "P5 \u2014 Conversation reporting for the connected agent\nUse the dedicated sample-data FUB account supplied through secure reviewer credentials, connected to https://fub-mcp.zillow.com/ with the submitted four skills. Start a fresh chat and select Follow Up Boss. Resolve IDs from live tool results. Do not create an account or reset sample records. \nExisting baseline: The dedicated demo account's independently inspected public call collection on November 6 had no qualifying calls for November 1, 2026 00:00:00\u201323:59:59 UTC. Expected count for that unchanged historical interval is zero; the only inspected call was outside the interval and seven seconds long. No new call fixture is needed. Keep this historical interval unchanged during review.\nExecution: Run the prompt, compare the report user, exact UTC bounds, zero-count baseline and coverage. If the account or historical call records changed, record a fresh independent baseline before asserting an exact count; do not invent a replacement expectation.\nEvidence scope: The recording and separate read-only report corroboration support the zero case. The combined video includes a close-up of the existing report, not a second execution. This does not test a nonzero 120-second threshold boundary.",
              "prompt": "How many conversations did I have in Follow Up Boss on November 1, 2026, from 00:00:00 through 23:59:59 UTC? Explain what counts as a conversation and tell me whether the result is complete.",
              "tools_triggered": "mcp_app_get-current-user; mcp_app_get_agent_conversation_count",
              "expected_behavior": "Resolve the authenticated FUB user and call mcp_app_get_agent_conversation_count with agentId set to that returned integer ID, start=\"2026-11-01T00:00:00Z\", and end=\"2026-11-01T23:59:59Z\". Define a conversation as an active public call lasting at least 120 seconds and attributed by userId. Show the count returned by the report, preserving a genuine zero. For complete coverage, the count must match the independently recorded baseline; exclude shorter calls, other users and out-of-window calls. For partial coverage, label the result as a lower bound and the exact-count assertion as inconclusive. Render the report without a card-loading error. Do not call activity totals a conversation count, infer an unreturned count, or write CRM data."
            }
          ],
          "negative": [
            {
              "description": "N1 \u2014 General CRM advice. Fresh chat, FUB installed and available for automatic selection, with no forced @FUB mention. No fixtures required. Expected: Explain the general concepts directly. No FUB discovery, authentication prompt, account read, widget or write. CRM terminology alone does not require private account access.",
              "prompt": "What is the difference between a CRM contact, a lead, and an opportunity?"
            },
            {
              "description": "N2 \u2014 Editing supplied outreach text. Fresh chat, FUB installed and available for automatic selection, with no forced @FUB mention. No fixtures required. Expected: Rewrite only the supplied text. Do not search for Taylor, retrieve notes, invoke FUB drafting tools, save a draft or send anything. The supplied text is sufficient.",
              "prompt": "Make this follow-up email warmer and shorter: \"Hi Taylor, checking whether you had time to review the buyer checklist. Let me know if you have any questions.\""
            },
            {
              "description": "N3 \u2014 Property search outside this integration. Fresh chat, FUB installed and available for automatic selection, with no forced @FUB mention. No fixtures required. Expected: Do not invoke any FUB tools or search CRM contacts as if they were property listings. Use an appropriate property-search capability if independently available; otherwise explain the need for current listing data. Do not fabricate listings or availability.",
              "prompt": "Find three homes currently for sale in Seattle under $800,000 with at least three bedrooms."
            }
          ]
        },
        "commerce": false,
        "commerce_description": "Uses an existing Follow Up Boss account. The plugin does not support purchases, payments, or upgrades.",
        "prompts": [
          "Which Follow Up Boss user am I connected as? Give me my morning brief with today\u2019s appointments, tasks due today, overdue tasks, and any leads needing a response or follow-up. Include my timezone and any coverage limitations.",
          "Find FUB Review Buyer in Follow Up Boss and show the latest two notes. If more than one person matches, let me choose before opening the notes.",
          "Find up to three Follow Up Boss contacts tagged FUB Plugin Review and draft a personalized email for each to schedule a consultation. Use their recent notes and keep everything as drafts for me to review.",
          "For the Follow Up Boss contact with email buyer.a@example.com, prepare a note with the text \"Demo review only: buyer requested the preparation checklist before our consultation.\" and a task assigned to me, due tomorrow at 10:00 AM in my FUB timezone. Use \"QA review follow-up\" as the note title and \"QA review buyer checklist\" as the task title, appending the same unique timestamp suffix to both so this run is distinguishable from earlier tests. Check for matching existing records first. Show the exact titles and let me review both changes before saving.",
          "How many conversations did I have in Follow Up Boss on November 1, 2026, from 00:00:00 through 23:59:59 UTC? Explain what counts as a conversation and tell me whether the result is complete."
        ],
        "demo_recording_url": "https://youtu.be/0ZdxtWsdyro"
      },
      "apps": "./.app.json"
    }
  },
  "homepage": "https://www.followupboss.com/",
  "keywords": [
    "crm",
    "real-estate",
    "contacts",
    "follow-up",
    "mcp",
    "skills",
    "tasks",
    "reporting"
  ],
  "name": "follow-up-boss",
  "version": "0.2.5"
}

SHA-256: 3e30d641a8c03dedbab6bce2c3db3949ae3e0b49cb0e3ba9c03923c2ae3e10be