Fictura

Full-text search across the Fictura docs, grouped by page. Use this before answering any 'how do I…' question about the SDK, API, paywalls, entitlements, links or webhooks — the docs are the source of truth and are regenerated on every code change. Returns page paths; pass one to read_doc for the full text. No API key required.

{
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "minLength": 1,
      "maxLength": 200,
      "description": "What to search for, e.g. 'purchases adapter'"
    },
    "limit": {
      "description": "Max pages to return (default 8)",
      "type": "integer",
      "minimum": 1,
      "maximum": 20
    }
  },
  "required": [
    "query"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

The full documentation index — every page path, grouped by section, with a one-line description. Use it to find the right page when a search term is hard to guess. No API key required.

{
  "type": "object",
  "properties": {},
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

The complete markdown of one documentation page. Accepts a site-relative path such as '/implementation/welcome/sdk-quickstart' (a full docs.fictura.co URL works too). If the path is wrong, the closest real paths come back as suggestions. No API key required.

{
  "type": "object",
  "properties": {
    "path": {
      "type": "string",
      "minLength": 1,
      "maxLength": 300,
      "description": "Page path, e.g. /implementation/sdk-reference/expo-react-native"
    }
  },
  "required": [
    "path"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

The real values needed to wire the Fictura SDK into a codebase: the API base URL, this app's publishable SDK key (gk_…), and the RevenueCat webhook URL. ALWAYS call this before generating integration code — never leave a placeholder API key in what you write. The SDK key is publishable and safe to commit in app source; it identifies the app, not a person.

{
  "type": "object",
  "properties": {},
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

What is actually configured for this app: the setup checklist, every Fictura feature toggle and whether it is on, and which third-party integrations (Stripe, RevenueCat, Slack, Sentry, App Store Connect, …) are connected. Use it to check whether a feature is enabled before writing code that depends on it — a disabled tool is a server-side kill switch the SDK obeys.

{
  "type": "object",
  "properties": {},
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

This app's real numbers. `overview` gives headline metrics (users, trials, trial→paid rate, events by name, cancel reasons, 14-day activity). `funnel` gives the ordered conversion funnel with per-step drop-off. `cohorts` compares behaviour across billing outcomes — what converted users did that cancelled users didn't. Below ~100 users in a step the sample is too small to read. `stores` splits paying users, purchases and revenue by App Store / Google Play / web and by storefront country (last 28 days).

{
  "type": "object",
  "properties": {
    "view": {
      "type": "string",
      "enum": [
        "overview",
        "funnel",
        "cohorts",
        "stores"
      ],
      "description": "Which analytics view to return"
    }
  },
  "required": [
    "view"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

Where installs and revenue actually came from. `summary` is the headline attribution picture (installs, organic vs non-organic, revenue). `kpis` breaks the same window down by source, campaign, link or day. `installs` lists individual installs with their attribution. Defaults to the trailing 28 days.

{
  "type": "object",
  "properties": {
    "view": {
      "type": "string",
      "enum": [
        "summary",
        "kpis",
        "installs"
      ],
      "description": "Which report to return"
    },
    "since": {
      "description": "YYYY-MM-DD (default 28 days ago)",
      "type": "string"
    },
    "until": {
      "description": "YYYY-MM-DD (default today)",
      "type": "string"
    },
    "group_by": {
      "description": "For view=kpis (default source)",
      "type": "string",
      "enum": [
        "source",
        "campaign",
        "link",
        "day"
      ]
    },
    "limit": {
      "description": "For view=installs (default 100)",
      "type": "integer",
      "minimum": 1,
      "maximum": 500
    }
  },
  "required": [
    "view"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

The app's users, most recently active first — each with an identity label, event count, last seen, and derived churn state (in_trial, converted, cancelled, expired, billing_issue, grace_period, paused, refunded, none). Capped so a large app does not flood the context; `total` reports how many matched before the cap.

{
  "type": "object",
  "properties": {
    "limit": {
      "description": "Max users (default 50)",
      "type": "integer",
      "minimum": 1,
      "maximum": 200
    },
    "churn_state": {
      "description": "Only users in this billing state",
      "type": "string",
      "enum": [
        "in_trial",
        "converted",
        "cancelled",
        "expired",
        "billing_issue",
        "grace_period",
        "paused",
        "refunded",
        "none"
      ]
    }
  },
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

One user's identity (every stitched device / account / RevenueCat id), event breakdown, churn state and recent activity. Accepts the Fictura master user id, or any identifier the app knows them by — a device id, account id or RevenueCat id.

{
  "type": "object",
  "properties": {
    "user_id": {
      "type": "string",
      "minLength": 1,
      "maxLength": 200,
      "description": "Master user id, or any known identifier"
    }
  },
  "required": [
    "user_id"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

The authoritative paid/not-paid verdict for one user, unified across Stripe, RevenueCat, App Store and Play — the same answer GET /api/v1/entitlements/{user_id} returns to a server. Note: `environment` is SANDBOX when the verdict rests on test purchases, so always check it before granting production access; a cancellation only flips will_renew (access runs to expires_at); and an unknown user is a valid 'none' answer, not an error.

{
  "type": "object",
  "properties": {
    "user_id": {
      "type": "string",
      "minLength": 1,
      "maxLength": 200,
      "description": "Device id, account id or RevenueCat id"
    }
  },
  "required": [
    "user_id"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

Every event this app has ever sent, with volume, last-seen, and whether capture is switched off. Use it before adding instrumentation so you reuse the existing event name instead of introducing a near-duplicate — the name chosen here is the same string an experiment later names as its primary metric.

{
  "type": "object",
  "properties": {},
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

Every paywall and onboarding flow, what is actually being served at each placement (running experiment > live > none), and the valid placement names. IMPORTANT: read `placements` before writing a placement string into code. The list is configured ∪ observed, so a name that appears only under `observed` is usually a typo in the app — and a placement that does not exist renders nothing at all, with no error.

{
  "type": "object",
  "properties": {},
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

The full configuration of one paywall or onboarding flow, plus its version history. Note that configs never contain price strings — prices resolve at render time from the PurchasesAdapter's packages, so never copy a price literal out of (or into) a config.

{
  "type": "object",
  "properties": {
    "kind": {
      "type": "string",
      "enum": [
        "paywall",
        "onboarding"
      ],
      "description": "Which kind of surface"
    },
    "id": {
      "type": "string",
      "format": "uuid",
      "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
      "description": "The surface id, from list_surfaces"
    }
  },
  "required": [
    "kind",
    "id"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

The one-click starter templates available for paywalls or onboarding flows, with the template key and what each looks like. Use this when asked to add a paywall so you pick a real template key rather than inventing one.

{
  "type": "object",
  "properties": {
    "kind": {
      "type": "string",
      "enum": [
        "paywall",
        "onboarding"
      ],
      "description": "Which template catalog"
    }
  },
  "required": [
    "kind"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

Every experiment with status and, for running or finished ones, full Bayesian results — exposures, conversions, and the probability each variant is best.

{
  "type": "object",
  "properties": {},
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

One experiment with its variants and full Bayesian results.

{
  "type": "object",
  "properties": {
    "id": {
      "type": "string",
      "format": "uuid",
      "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
      "description": "Experiment id, from list_experiments"
    }
  },
  "required": [
    "id"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

`roas` gives per-campaign spend, attributed installs/trials/paying users, revenue, CPI, CAC and ROAS, plus blended totals and explicitly-unattributed revenue — always keep attributed and blended figures apart when reporting these. `spend` gives raw daily ad-spend rows. `links` lists this app's tracking links.

{
  "type": "object",
  "properties": {
    "view": {
      "type": "string",
      "enum": [
        "roas",
        "spend",
        "links"
      ],
      "description": "Which acquisition view"
    },
    "since": {
      "description": "YYYY-MM-DD, for view=roas",
      "type": "string"
    },
    "until": {
      "description": "YYYY-MM-DD, for view=roas",
      "type": "string"
    },
    "provider": {
      "description": "Filter, for view=spend",
      "type": "string"
    },
    "days": {
      "description": "Lookback, for view=spend",
      "type": "integer",
      "minimum": 1,
      "maximum": 90
    }
  },
  "required": [
    "view"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

Store-reported numbers synced from Appfigures: downloads, re-downloads, updates, uninstalls, store revenue after the store's cut (subscriptions, in-app purchases, ads), top countries, the ratings snapshot, recent reviews with text, and category chart positions. Money is in micros of `currency`. Store revenue is a separate figure from RevenueCat revenue; never add the two. Returns connected: false when Appfigures is not set up.

{
  "type": "object",
  "properties": {
    "days": {
      "description": "Lookback in days, default 28",
      "type": "integer",
      "minimum": 1,
      "maximum": 1095
    },
    "reviews": {
      "description": "How many recent reviews to include, default 20",
      "type": "integer",
      "minimum": 0,
      "maximum": 200
    }
  },
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

Campaigns read live from a connected ad platform: status, daily budget and ad sets. Returns a not_connected result rather than failing when the provider is not set up. This calls the provider's API, so prefer get_acquisition_report for historical numbers.

{
  "type": "object",
  "properties": {
    "provider": {
      "type": "string",
      "enum": [
        "meta",
        "apple_search_ads",
        "snapchat",
        "tiktok",
        "google_ads",
        "reddit",
        "test"
      ],
      "description": "Which ad platform"
    }
  },
  "required": [
    "provider"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

Creator records with a 28-day funnel per creator (clicks, installs, trials, paying users) and the tracking links tagged to each.

{
  "type": "object",
  "properties": {},
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

How links reach the app. `app_links` is the most important for integration work: it returns the iOS team id, bundle id, Android package and SHA-256 fingerprints that Fictura serves in the Universal Links / App Links association files, plus ios_ready and android_ready. Get these wrong and BOTH files fail SILENTLY — they parse, associate nothing, report no error, and links simply keep opening the browser instead of the app, so verify the ready flags rather than assuming. `domains` lists branded link domains and their DNS verification state, `web_config` the web-to-app smart banner, `esp` the email provider link setup.

{
  "type": "object",
  "properties": {
    "view": {
      "type": "string",
      "enum": [
        "app_links",
        "domains",
        "web_config",
        "esp"
      ],
      "description": "Which part of the link setup"
    }
  },
  "required": [
    "view"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

Whether push is set up and who could receive it: registered-device counts per billing cohort (all / paid / trial / free) and whether OneSignal is configured. Returns counts and configuration only — never device tokens or individual recipients.

{
  "type": "object",
  "properties": {},
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

This app's auto-renewable subscriptions in App Store Connect: product id, billing period and Apple review state. Use it to check that a paywall references a product that actually exists. Pass subscription_id to also fetch Apple's price ladder for that one product (Apple scopes price points per subscription, so there is no global list).

{
  "type": "object",
  "properties": {
    "subscription_id": {
      "description": "Also return price points for this subscription",
      "type": "string"
    },
    "territory": {
      "description": "Territory for price points (default USA)",
      "type": "string"
    }
  },
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

The error feed: grouped issues with level, status, event and user counts, a 14-day sparkline, plus the app's uptime summary. Defaults to unresolved issues only. `synthetic: true` marks console lines the SDK captured, not crashes.

{
  "type": "object",
  "properties": {
    "status": {
      "description": "Which issues to include (default unresolved)",
      "type": "string",
      "enum": [
        "unresolved",
        "resolved",
        "ignored",
        "discarded",
        "all"
      ]
    },
    "include_legacy": {
      "description": "Also list issues grouped before grouping v2 (default false)",
      "type": "boolean"
    }
  },
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

One issue in full: the group, its 50 most recent occurrences with stack traces, release and environment, and 30 days of daily counts. This is the tool to reach for when asked to fix a production error. When the app uploaded source maps, each occurrence also has `stack_resolved` and `frames` (original file, line, column and function; `in_app` marks the app's own code) — read those instead of the minified `stack`. An occurrence with a trace_id can be opened with get_trace.

{
  "type": "object",
  "properties": {
    "issue_id": {
      "type": "string",
      "format": "uuid",
      "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
      "description": "Issue id, from list_error_issues"
    }
  },
  "required": [
    "issue_id"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

Find issues by text in the title or culprit, platform, or release (first or last seen in). Returns the same rows as list_error_issues, filtered.

{
  "type": "object",
  "properties": {
    "query": {
      "description": "Text to look for in the title or culprit",
      "type": "string",
      "maxLength": 200
    },
    "status": {
      "type": "string",
      "enum": [
        "unresolved",
        "resolved",
        "ignored",
        "discarded",
        "all"
      ]
    },
    "platform": {
      "type": "string",
      "maxLength": 20
    },
    "release": {
      "type": "string",
      "maxLength": 200
    },
    "limit": {
      "type": "integer",
      "minimum": 1,
      "maximum": 100
    }
  },
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

One issue condensed for fixing it: latest stack (resolved when source maps exist), in-app frames, breadcrumbs before it, facets (release, OS, device, screen), cause chain, and a ready-to-use fix prompt.

{
  "type": "object",
  "properties": {
    "issue_id": {
      "type": "string",
      "format": "uuid",
      "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
      "description": "Issue id, from list_error_issues"
    }
  },
  "required": [
    "issue_id"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

Resolve, ignore or reopen an issue, assign it, set its priority, or add a note. Only works when the app allows MCP writes (Issues settings → Let MCP keys change issues).

{
  "type": "object",
  "properties": {
    "issue_id": {
      "type": "string",
      "format": "uuid",
      "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
    },
    "status": {
      "type": "string",
      "enum": [
        "resolved",
        "ignored",
        "ongoing"
      ]
    },
    "resolved_in_release": {
      "type": "string",
      "maxLength": 200
    },
    "assignee": {
      "anyOf": [
        {
          "type": "string",
          "maxLength": 200
        },
        {
          "type": "null"
        }
      ]
    },
    "priority": {
      "anyOf": [
        {
          "type": "string",
          "enum": [
            "high",
            "medium",
            "low"
          ]
        },
        {
          "type": "null"
        }
      ]
    },
    "note": {
      "type": "string",
      "minLength": 1,
      "maxLength": 4000
    }
  },
  "required": [
    "issue_id"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

Every span of one trace (app → backend → dependencies) as a tree: names, services, start offsets, durations, HTTP status and errors, plus the error events linked to the trace. Take the trace_id from an occurrence in get_error_issue. Use it to see where the time went or what failed first.

{
  "type": "object",
  "properties": {
    "trace_id": {
      "type": "string",
      "description": "32-character hex W3C trace id"
    }
  },
  "required": [
    "trace_id"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

The JSON document a Studio (visual editor) paywall is made of, with its status and version, plus the reference to the document model. Read this before save_paywall_doc, and edit the document you got rather than writing one from scratch — keep node ids, change only what was asked. Prices are never typed: use {{ products.<slot>.price }} and the other product variables.

{
  "type": "object",
  "properties": {
    "id": {
      "type": "string",
      "format": "uuid",
      "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
      "description": "The paywall id, from list_surfaces"
    }
  },
  "required": [
    "id"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

Runs a document through the same parser and renderer a save uses and reports what is wrong, if anything. Changes nothing.

{
  "type": "object",
  "properties": {
    "doc": {
      "type": "object",
      "propertyNames": {
        "type": "string"
      },
      "additionalProperties": {},
      "description": "A paywall document (version: 1)"
    }
  },
  "required": [
    "doc"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

Replaces a draft paywall's document with the one given, as a new version (History in the dashboard shows it as `mcp: <note>` and can roll it back). Refused for a live paywall — copy it in the dashboard first. Needs an MCP key that can edit. Products, translations and other settings are kept.

{
  "type": "object",
  "properties": {
    "id": {
      "type": "string",
      "format": "uuid",
      "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
      "description": "The draft paywall's id"
    },
    "doc": {
      "type": "object",
      "propertyNames": {
        "type": "string"
      },
      "additionalProperties": {},
      "description": "The complete edited document"
    },
    "note": {
      "description": "What changed, for the version history",
      "type": "string",
      "maxLength": 160
    }
  },
  "required": [
    "id",
    "doc"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

Creates a draft paywall from a Studio template (template_key, from list_templates — the webview ones) or from a document you wrote. It is never made live: going live is done in the dashboard. Needs an MCP key that can edit.

{
  "type": "object",
  "properties": {
    "name": {
      "type": "string",
      "minLength": 1,
      "maxLength": 80,
      "description": "The paywall's name in the dashboard"
    },
    "template_key": {
      "description": "A webview template key to start from",
      "type": "string",
      "maxLength": 80
    },
    "doc": {
      "description": "A complete document, instead of a template",
      "type": "object",
      "propertyNames": {
        "type": "string"
      },
      "additionalProperties": {}
    }
  },
  "required": [
    "name"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

Connects to the paywall editor a person has open, using the 6-character code shown under “Pair an agent” in the Studio. Returns a pairing_id for the editor_* tools. The code works once and for 10 minutes; a pairing lasts 24 hours or until either side stops it.

{
  "type": "object",
  "properties": {
    "code": {
      "type": "string",
      "minLength": 4,
      "maxLength": 12,
      "description": "The code shown in the editor"
    }
  },
  "required": [
    "code"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

The document exactly as it is on the person's screen (unsaved changes included), which paywall it is, the screen they are on and the node they have selected, plus the document model reference. Read this before editor_set_doc and edit what you got — keep node ids, change only what was asked.

{
  "type": "object",
  "properties": {
    "pairing_id": {
      "type": "string",
      "minLength": 8,
      "maxLength": 80,
      "description": "From pair_editor"
    }
  },
  "required": [
    "pairing_id"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

Replaces the document in the person's open editor with the one given. It is NOT saved: the person sees the change, can undo it, and saves it themselves. The document is validated first and refused with the problems if it does not parse. Needs an MCP key that can edit.

{
  "type": "object",
  "properties": {
    "pairing_id": {
      "type": "string",
      "minLength": 8,
      "maxLength": 80,
      "description": "From pair_editor"
    },
    "doc": {
      "type": "object",
      "propertyNames": {
        "type": "string"
      },
      "additionalProperties": {},
      "description": "The complete edited document"
    },
    "note": {
      "description": "What changed, shown to the person in the editor",
      "type": "string",
      "maxLength": 160
    }
  },
  "required": [
    "pairing_id",
    "doc"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

Stops this pairing. The editor shows that the agent left.

{
  "type": "object",
  "properties": {
    "pairing_id": {
      "type": "string",
      "minLength": 8,
      "maxLength": 80,
      "description": "From pair_editor"
    }
  },
  "required": [
    "pairing_id"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

The JSON document a builder-made onboarding flow is made of, with its status and version, plus the reference to the document model. Read this before save_onboarding_doc, and edit the document you got rather than writing one from scratch — keep step keys and node ids, change only what was asked.

{
  "type": "object",
  "properties": {
    "id": {
      "type": "string",
      "format": "uuid",
      "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
      "description": "The onboarding flow id, from list_surfaces"
    }
  },
  "required": [
    "id"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

Runs a document through the same parser, step-key check and renderer a save uses and reports what is wrong, if anything. Changes nothing.

{
  "type": "object",
  "properties": {
    "doc": {
      "type": "object",
      "propertyNames": {
        "type": "string"
      },
      "additionalProperties": {},
      "description": "An onboarding document (version: 1)"
    }
  },
  "required": [
    "doc"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

Replaces a draft flow's document with the one given, as a new version (the dashboard's history shows it as `mcp: <note>` and can roll it back). Refused for a live flow. Needs an MCP key that can edit. Translations, overrides and the exit setting are kept.

{
  "type": "object",
  "properties": {
    "id": {
      "type": "string",
      "format": "uuid",
      "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
      "description": "The draft flow's id"
    },
    "doc": {
      "type": "object",
      "propertyNames": {
        "type": "string"
      },
      "additionalProperties": {},
      "description": "The complete edited document"
    },
    "note": {
      "description": "What changed, for the version history",
      "type": "string",
      "maxLength": 160
    }
  },
  "required": [
    "id",
    "doc"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

Creates a draft onboarding flow from a document you wrote (see get_onboarding_doc's reference). It is never made live: going live is done in the dashboard. Needs an MCP key that can edit.

{
  "type": "object",
  "properties": {
    "name": {
      "type": "string",
      "minLength": 1,
      "maxLength": 80,
      "description": "The flow's name in the dashboard"
    },
    "doc": {
      "type": "object",
      "propertyNames": {
        "type": "string"
      },
      "additionalProperties": {},
      "description": "A complete onboarding document"
    }
  },
  "required": [
    "name",
    "doc"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

Import everything AppsFlyer holds for this app: installs and the channel, campaign, adset and ad behind each one, in-app events and purchases, uninstalls, reinstalls, ad revenue and retargeting traffic. All twelve raw-data reports are walked; ones the AppsFlyer plan lacks are skipped, not failed. Runs in the background and keeps going after this call. mode 'auto' (default) only pulls the days since the last finished import when there is one, and walks the full history otherwise. 'full' re-walks everything. resume=true continues a failed or cancelled run from where it stopped. Safe to call while a run is going: it reports that run instead of starting another. Anything already imported is counted once. Check progress with get_appsflyer_import_status.

{
  "type": "object",
  "properties": {
    "mode": {
      "description": "Default auto",
      "type": "string",
      "enum": [
        "auto",
        "full"
      ]
    },
    "resume": {
      "description": "Continue the last failed or cancelled run",
      "type": "boolean"
    }
  },
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

Whether AppsFlyer is connected, the latest import run (status, progress, rows imported, duplicates skipped, people created, date range covered, error if it stopped), and whether an import has ever finished. Call before start_appsflyer_import so a finished import is not offered again as though nothing had happened.

{
  "type": "object",
  "properties": {},
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

What the AppsFlyer import brought in about where people came from: people with an imported attribution, split by media source (organic included) and acquisition vs retargeting, plus the top campaigns. Filters on the install date. Imported verdicts never overwrite an attribution Fictura's own SDK resolved. For revenue and ROAS by source, use get_attribution_report with view=kpis.

{
  "type": "object",
  "properties": {
    "since": {
      "description": "Install date from, YYYY-MM-DD",
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$"
    },
    "until": {
      "description": "Install date to, YYYY-MM-DD",
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$"
    },
    "top_campaigns": {
      "description": "Default 20",
      "type": "integer",
      "minimum": 1,
      "maximum": 100
    }
  },
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}