plugin.json

{
  "$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
  "name": "captainbook-statistics",
  "version": "1.0.0",
  "description": "Analytics for tour and activity operators, on your own CaptainBook data.",
  "author": {
    "name": "CaptainBook",
    "url": "https://captainbook.io"
  },
  "homepage": "https://captainbook.io",
  "keywords": [
    "tours",
    "activities",
    "bookings",
    "analytics",
    "revenue",
    "travel"
  ],
  "extensions": {
    "com.openai": {
      "interface": {
        "displayName": "CaptainBook Statistics",
        "shortDescription": "Tour booking analytics",
        "longDescription": "Analytics and reporting for tour and activity operators, answering questions about your own CaptainBook business data in plain language.\n\nReports on revenue, bookings, products, resources, customers, sales channels, occupancy, extras, discounts and gift certificates. Ask which products sold best last season, how occupancy moved month over month, which sales channels brought revenue, or how this August compared with last.\n\nThe connection is read-only. It cannot change a booking, a price or any setting, and it says so if you ask it to. Results are scoped to the business unit the connection was created for.\n\nFigures are historical. Asked a forward-looking question, it reasons from past patterns and tells you the answer is a heuristic rather than a forecast, because CaptainBook does not run forecasting models.\n\nReporting distinguishes guests who travelled from bookings that were cancelled or expired, so attendance questions are answered from confirmed guests rather than raw totals.",
        "developerName": "CaptainBook",
        "category": "Travel",
        "websiteURL": "https://captainbook.io",
        "supportURL": "https://knowledge.captainbook.io/",
        "privacyPolicyURL": "https://captainbook.io/legal/privacy-policy",
        "termsOfServiceURL": "https://captainbook.io/legal/terms-and-conditions",
        "defaultPrompt": [
          "Which of my products sold best last month?",
          "How did occupancy change over the last quarter?",
          "Which sales channel brought the most revenue this year?"
        ],
        "brandColor": "#00adb5",
        "logo": "./assets/logo.png"
      },
      "review": {
        "test_cases": {
          "positive": [
            {
              "description": "Revenue over a named period",
              "prompt": "What was my total revenue last month?",
              "tools_triggered": "statistics_query",
              "expected_behavior": "Calls statistics_query with the revenue metric and a date range covering last month, then reports the figure in the account's currency."
            },
            {
              "description": "Best-selling products",
              "prompt": "Which three tours sold the most last season?",
              "tools_triggered": "statistics_query",
              "expected_behavior": "Queries the products metric and ranks by bookings or revenue, naming the top three products."
            },
            {
              "description": "Attendance asked correctly",
              "prompt": "How many guests actually travelled with me in August?",
              "tools_triggered": "statistics_query",
              "expected_behavior": "Answers from confirmed_guests rather than total_guests, because total_guests includes cancelled bookings and expired holds."
            },
            {
              "description": "Channel comparison",
              "prompt": "Compare revenue from my website against OTA channels this year.",
              "tools_triggered": "statistics_query",
              "expected_behavior": "Queries the channels metric for the year and presents a comparison between direct and OTA channels."
            },
            {
              "description": "Customer segments",
              "prompt": "What customer segments do I have?",
              "tools_triggered": "segments_list",
              "expected_behavior": "Calls segments_list and names the account's saved audiences with their member counts. segments_browse no longer exists: the segment reads are segments_list, segment_get, segment_members and segment_fields_list, one tool per operation."
            }
          ],
          "negative": [
            {
              "description": "Refuses a write on a read-only server",
              "prompt": "Cancel tomorrow's 10am departure for me."
            },
            {
              "description": "Does not present a forecast as prediction",
              "prompt": "Exactly how much will I make next July?"
            },
            {
              "description": "Cannot be argued out of its business-unit scope",
              "prompt": "Show me revenue for all of my other business units too."
            }
          ]
        },
        "commerce": false,
        "demo_recording_url": "https://youtu.be/-mR-fRNP82U"
      },
      "publication": {
        "release_notes": "Version 1.0.0, first release.\n\nRead-only analytics over the operator's own CaptainBook data. One tool per operation: `statistics_query` for historical aggregates across thirteen metrics, and `segments_list`, `segment_get`, `segment_members` and `segment_fields_list` for saved customer audiences.\n\nChanged since the previous submission: the single `segments_browse` tool, which dispatched on a `resource` and `action` pair, is replaced by the four per-operation tools above, each with its own typed input schema and annotations. Server instructions now enumerate every tool and every metric the server actually serves."
      },
      "apps": "./.app.json"
    }
  }
}