VybeOS

Add one or more blank output slots to an EXISTING campaign. ``outputs`` is the slot manifest: a list of ``{"platform_type_id": <int>, "count": <int>}`` (each count >= 1); that many empty slots are created per platform type (discover the ids with ``vybe_list_platform_types``). The new slots start empty — fill each one's copy with ``vybe_edit_content_output_content`` and set its schedule with ``vybe_update_content_output``. The campaign's status and narrative are left unchanged. All-or-nothing: an unknown ``platform_type_id`` for this brand is rejected up front and nothing is created. Requires ``brand:edit``.

vybe_add_content_output

Cancel a running task for a brand (best effort). Requires brand:edit.

vybe_task_cancel

Create a campaign and its empty content-output slots in one call. VybeOS does not generate anything — the campaign is created *empty* and you author every part of it from your AI tool. ``outputs`` is the slot manifest: a list of ``{"platform_type_id": <int>, "count": <int>}`` (each count >= 1); that many blank output slots are created per platform type. Discover the ``platform_type_id``s available to this brand with ``vybe_list_platform_types``. ``category`` is the campaign type; ``product_ids`` / ``persona_ids`` (UUIDs from the brand) associate products and personas — note some categories (e.g. ``product_launch``) require at least one ``product_id``. There is no scheduling step: the plan, its blank slots, and a draft narrative are all created in one synchronous call. Then fill the work — set the narrative with ``vybe_update_campaign_narrative`` and fill each slot's copy with ``vybe_edit_content_output_content`` (list slots via ``vybe_list_content_outputs``, which advertises the fillable fields). Requires ``brand:edit``. If slot creation fails the just-created campaign is rolled back (deleted) so no empty, slot-less campaign is leaked, and the call returns an ``error``.

vybe_create_campaign

Describe everything ``vybe_create_campaign`` needs — call this first. Returns the create contract so a campaign can be created in a single ``vybe_create_campaign`` call without a failed round-trip: - ``required`` / ``optional``: the input fields and their shapes. - ``categories``: every campaign category with its label and ``requires_product`` — categories flagged ``true`` are rejected unless you pass at least one ``product_ids`` entry (this is the ``product_launch`` gotcha). Product data is not exposed to MCP connections, so there is no tool to discover product UUIDs: ask the user for them, or pick a category that does not require a product. - ``outputs``: discover the ``platform_type_id`` values with ``vybe_list_platform_types`` (the same ``brand_id``); each output is ``{"platform_type_id": <int>, "count": <int>}`` and creates that many blank slots. No scheduling — slots are created empty for you to fill.

vybe_describe_campaign_input

Author or edit a campaign's narrative content for a brand. VybeOS does not generate the narrative — you write it. If the campaign has no narrative yet, an empty DRAFT is created on first write (upsert), so this is also how you author it from scratch. ``updates`` keys must be narrative fields for this campaign's mode (call ``vybe_get_campaign_narrative`` to see ``editable_fields`` AND ``editable_field_specs`` — the latter gives each field's value ``shape``, so a structured field like ``story_arc`` is authored as an object ``{"opening": ..., "rising_action": ..., "climax": ..., "resolution": ...}`` rather than plain text). Unknown keys are rejected, not silently written. Editing is only allowed while the narrative is in DRAFT status, and downstream creatives are NOT regenerated. Requires the ``brand:edit`` permission.

vybe_update_campaign_narrative

Fill or edit one output's copy (caption, headline, body, …). VybeOS does not generate copy — you author it and it lands here. The slot starts empty; the first call fills it (counts as the first edit) and you can edit it as many times as you like after. ``content`` keys must be in the output's ``editable_content_fields`` (from ``vybe_get_content_output``) — unknown keys are rejected, not written — and each value is validated against the platform's field constraints. Pass the ``version`` you read on get (optimistic lock); a ``version_conflict`` means someone else edited — re-read and retry. Requires ``brand:edit``.

vybe_edit_content_output_content

Fetch one publication's detail for citation. The publication id identifies its brand; you are authorized for that brand and denied (not-found) if you cannot access it. No ``brand_id`` argument.

fetch

Start a long-running generation job for a brand. ``kind`` is one of: topics, personas. ``input`` is the generator's input payload (validated against the processor's schema). Returns a task handle — poll ``vybe_task_status`` with the ``task_id``. Requires the ``brand:edit`` permission.

vybe_generate

Get a campaign (content plan): fields, status, product/persona links. The campaign's narrative is a separate resource — read it with ``vybe_get_campaign_narrative``.

vybe_get_campaign

Get the narrative for a campaign (content plan) of a brand. ``editable_fields`` are the narrative keys you may author via ``vybe_update_campaign_narrative``; ``editable_field_specs`` maps each to its value ``shape`` (``scalar`` / ``list_of_strings`` / ``object`` / ``dict_of_objects``) — and, for object shapes, the nested ``fields`` (e.g. ``story_arc`` → ``opening`` / ``rising_action`` / ``climax`` / ``resolution``), so you author the right value TYPE in one shot instead of sending a structured field as plain text.

vybe_get_campaign_narrative