Update to Fullstory

{
  "canonical_app_id": "asdk_app_6a9a1ebb11fc81919ef2aa7231b9b068",
  "connector_id": "asdk_app_6a9a1ebb11fc81919ef2aa7231b9b068",
  "created_at": "2026-09-04T01:28:27.144530Z",
  "discoverability": "LISTED",
  "id": "plugin_asdk_app_6a9a1ebb11fc81919ef2aa7231b9b068",
  "is_template": false,
  "is_template_instance": false,
  "name": "app-6a9a1ebb11fc81919ef2aa7231b9b068",
  "release": {
    "app_ids": [
      "asdk_app_6a9a1ebb11fc81919ef2aa7231b9b068"
    ],
    "app_manifest": {
      "apps": {
        "fullstory": {
          "id": "asdk_app_6a9a1ebb11fc81919ef2aa7231b9b068",
          "required": true
        }
      }
    },
    "app_templates": [],
    "description": "See what actually happened behind every number.\n\nFullstory MCP gives ChatGPT and Codex both halves of product investigation: analytics to size a problem and session replay to see why it happened. Ask where checkout is leaking, why a metric moved, or how to reproduce a bug. It discovers your pages and elements, computes the metric or funnel, and opens the sessions behind the drop. Every answer links to Fullstory, so you can check the work in one click.\n\nFullstory shows what users experienced - including silent failures that never threw an error - so \"conversion dropped 12%\" becomes \"the coupon field fails 5x more for logged-out users.\"\n\nBecause every answer links to the proof, you can give ChatGPT or Codex a standing job. Set up a scheduled task once, and it reports back with the sessions attached: an hourly watch for silent failures, automatic bug scoping on new tickets, or a Monday ranking of the fixes that would recover the most users.\n\nWhat ChatGPT and Codex can do:\n\n(1) Map a session, then zoom to the moment. Read a compact timeline first, then jump to the timestamp where it broke to pull the screenshot and page DOM from before and after - keeping context light.\n\n(2) Review sessions at scale. Because sessions load as compact structured data, read dozens of replays in one run and surface why users gave up.\n\n(3) Build segments, metrics, and funnels in your own words. Discover your pages, named elements, and events so questions map to your product.\n\n(4) Compute on demand. Run counts, rates, trends, funnels, journeys, and friction breakdowns by device, browser, geography, or user property.\n\nFullstory autocaptures clicks, page views, console and network errors, and frustration signals (rage and dead clicks), so many questions need no instrumentation at all.",
    "display_name": "Fullstory",
    "id": "pluginrel_98053c07633081918daf25836cead2e5",
    "interface": {
      "brand_color": null,
      "capabilities": [],
      "category": "Data & Analytics",
      "composer_icon_dark_url": null,
      "composer_icon_url": "https://files.openai.com/content?id=file_00000000e24c81f585368607ebb445dd",
      "default_prompt": "Every hour, find checkout sessions with frustration but no logged error, and flag anything new with a session link.",
      "default_prompts": [
        "Every hour, find checkout sessions with frustration but no logged error, and flag anything new with a session link.",
        "Find a session with a console error this week. Show me the screen where it broke, then count who else hit it.",
        "Find the page with the most rage clicks this week. Open 3 sessions and show me the screen where users got stuck."
      ],
      "developer_name": "Fullstory",
      "logo_url": "https://files.openai.com/content?id=file_00000000aa5481f5a7ccbddac6f3a897",
      "logo_url_dark": null,
      "long_description": "See what actually happened behind every number.\n\nFullstory MCP gives ChatGPT and Codex both halves of product investigation: analytics to size a problem and session replay to see why it happened. Ask where checkout is leaking, why a metric moved, or how to reproduce a bug. It discovers your pages and elements, computes the metric or funnel, and opens the sessions behind the drop. Every answer links to Fullstory, so you can check the work in one click.\n\nFullstory shows what users experienced - including silent failures that never threw an error - so \"conversion dropped 12%\" becomes \"the coupon field fails 5x more for logged-out users.\"\n\nBecause every answer links to the proof, you can give ChatGPT or Codex a standing job. Set up a scheduled task once, and it reports back with the sessions attached: an hourly watch for silent failures, automatic bug scoping on new tickets, or a Monday ranking of the fixes that would recover the most users.\n\nWhat ChatGPT and Codex can do:\n\n(1) Map a session, then zoom to the moment. Read a compact timeline first, then jump to the timestamp where it broke to pull the screenshot and page DOM from before and after - keeping context light.\n\n(2) Review sessions at scale. Because sessions load as compact structured data, read dozens of replays in one run and surface why users gave up.\n\n(3) Build segments, metrics, and funnels in your own words. Discover your pages, named elements, and events so questions map to your product.\n\n(4) Compute on demand. Run counts, rates, trends, funnels, journeys, and friction breakdowns by device, browser, geography, or user property.\n\nFullstory autocaptures clicks, page views, console and network errors, and frustration signals (rage and dead clicks), so many questions need no instrumentation at all.",
      "plugin_category_id": "data & analytics",
      "privacy_policy_url": "https://www.fullstory.com/legal/privacy-policy/",
      "screenshot_urls": [],
      "short_description": "Product analytics for agents.",
      "terms_of_service_url": "https://www.fullstory.com/legal/terms-and-conditions/",
      "website_url": "https://www.fullstory.com/"
    },
    "keywords": [],
    "onboarding_skill_name": null,
    "requires_local_executor": false,
    "skills": [
      {
        "description": "How to structure A vs B comparisons in Fullstory — when to use dimensionality (event/session properties) vs separate segments (user-level properties), and why the distinction matters for correctness.",
        "interface": {
          "brand_color": null,
          "default_prompt": null,
          "display_name": "comparisons",
          "icon_large_url": null,
          "icon_small_url": null,
          "iconography": "chart",
          "short_description": "How to structure A vs B comparisons in Fullstory — when to use dimensionality (event/session properties) vs separate segments (user-level properties), and why the distinction matters for correctness."
        },
        "name": "comparisons",
        "plugin_release_skill_id": "pluginrsk_6ae49e67d5188191a102cedfeb2bb031"
      },
      {
        "description": "Finds where users struggle on a page or flow and whether a suspected problem is real. Ranks Fullstory's frustration and error signals, separates real problems from buttons people are meant to click many times, measures how many users each problem affects, and uses session replays to show what happened. Use when someone asks where users are struggling, what is broken on a page or flow, for top pain points or a friction audit, why users give up at a step, whether a rage click is real, whether pages feel slow, whether people keep retrying, re-typing or going back and forth, whether a mobile app keeps crashing, or whether a problem from support tickets is widespread or affects only a few people.",
        "interface": {
          "brand_color": null,
          "default_prompt": null,
          "display_name": "friction-analysis",
          "icon_large_url": null,
          "icon_small_url": null,
          "iconography": "radar",
          "short_description": "Finds where users struggle on a page or flow and whether a suspected problem is real. Ranks Fullstory's frustration and error signals, separates real problems from buttons people are meant to click many times, measures how many users each problem affects, and uses session replays to show what happened. Use when someone asks where users are struggling, what is broken on a page or flow, for top pain points or a friction audit, why users give up at a step, whether a rage click is real, whether pages feel slow, whether people keep retrying, re-typing or going back and forth, whether a mobile app keeps crashing, or whether a problem from support tickets is widespread or affects only a few people."
        },
        "name": "friction-analysis",
        "plugin_release_skill_id": "pluginrsk_6ae49e686ef88191850c713cb6c7cec8"
      },
      {
        "description": "Fullstory analytics workflow — the default way to answer any question about user behavior. Use whenever someone asks how many, what percentage, which pages, whether something is trending, where users drop off, what users did before or after an action, or how two cohorts compare — and also when they describe a business question that needs numbers behind it without ever saying \"metric\", \"funnel\", or \"segment\". Covers building and computing metrics, segments, funnels, and journeys, verifying that what got built is what was actually asked for, and pulling sessions to explain why the numbers look the way they do. Not for reviewing one specific session, or for setting up capture and instrumentation.",
        "interface": {
          "brand_color": null,
          "default_prompt": null,
          "display_name": "general-analysis",
          "icon_large_url": null,
          "icon_small_url": null,
          "iconography": "chart",
          "short_description": "Fullstory analytics workflow — the default way to answer any question about user behavior. Use whenever someone asks how many, what percentage, which pages, whether something is trending, where users drop off, what users did before or after an action, or how two cohorts compare — and also when they describe a business question that needs numbers behind it without ever saying \"metric\", \"funnel\", or \"segment\". Covers building and computing metrics, segments, funnels, and journeys, verifying that what got built is what was actually asked for, and pulling sessions to explain why the numbers look the way they do. Not for reviewing one specific session, or for setting up capture and instrumentation."
        },
        "name": "general-analysis",
        "plugin_release_skill_id": "pluginrsk_6ae49e67f6dc8191bcced53771183675"
      },
      {
        "description": "Finds product improvement ideas a team has not already considered. Searches the metrics, segments and funnels the team already built, builds the ones that are missing, measures how many users each idea affects against a baseline, and pulls session replays as evidence. Returns 3 to 5 ranked proposals, each with what is new about it, a user count with its baseline, and replay links. Use when someone asks what to build next, how to improve a product area or flow, what the team is missing, for data-backed product ideas or proposals, or what changed after a release. If the user only wants the list of Fullstory Opportunities, call the Opportunities tools directly instead. For counts, rates and trends use general-analysis, for A vs B mechanics use comparisons, and for one session use session-review.",
        "interface": {
          "brand_color": null,
          "default_prompt": null,
          "display_name": "idea-generation",
          "icon_large_url": null,
          "icon_small_url": null,
          "iconography": "chart",
          "short_description": "Finds product improvement ideas a team has not already considered. Searches the metrics, segments and funnels the team already built, builds the ones that are missing, measures how many users each idea affects against a baseline, and pulls session replays as evidence. Returns 3 to 5 ranked proposals, each with what is new about it, a user count with its baseline, and replay links. Use when someone asks what to build next, how to improve a product area or flow, what the team is missing, for data-backed product ideas or proposals, or what changed after a release. If the user only wants the list of Fullstory Opportunities, call the Opportunities tools directly instead. For counts, rates and trends use general-analysis, for A vs B mechanics use comparisons, and for one session use session-review."
        },
        "name": "idea-generation",
        "plugin_release_skill_id": "pluginrsk_6ae49e67ae688191b92db14d347c1124"
      },
      {
        "description": "Use when diagnosing user-reported issues, investigating bugs, analyzing user behavior, or validating UI correctness using Fullstory session recordings.",
        "interface": {
          "brand_color": null,
          "default_prompt": null,
          "display_name": "session-review",
          "icon_large_url": null,
          "icon_small_url": null,
          "iconography": "radar",
          "short_description": "Use when diagnosing user-reported issues, investigating bugs, analyzing user behavior, or validating UI correctness using Fullstory session recordings."
        },
        "name": "session-review",
        "plugin_release_skill_id": "pluginrsk_6ae49e689fe08191b396f27e99831ded"
      }
    ],
    "version": "3.1.0"
  },
  "scope": "GLOBAL",
  "status": "ENABLED"
}