chieflab_post_launch_review

Active

declared in 0.3.0

[chieflab_* alias of chiefmo_post_launch_review] USE WHEN ≥24h has passed since chiefmo_publish_approved_post fired and the user asks 'how did the launch perform?', 'what worked?', 'metrics from my launch'. Closes the loop: pulls 24h+ engagement (likes / comments / views / shares / follower delta) for posts in the launch run + recommends next iteration (rewrite, refresh creative, double down, pause). Returns per-account analytics + top posts + best-time-to-post + a structured next-move recommendation brief.

Parameters schema

{
  "type": "object",
  "required": [
    "runId"
  ],
  "properties": {
    "runId": {
      "type": "string",
      "description": "The launchId returned by chiefmo_launch_product. Used to scope analytics to posts from that launch."
    },
    "accountIds": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Optional. Specific Zernio accountIds to pull analytics for. Defaults to all accounts that posted in this launch."
    },
    "outputMode": {
      "type": "string",
      "description": "\"context\" (default): returns metrics + a brief your LLM renders into the customer-facing recommendation. \"full\": ChiefLab generates the recommendation server-side."
    },
    "lookbackDays": {
      "type": "number",
      "description": "How many days of history to consider (default 7, max 90)."
    }
  }
}

What this tool wraps· 0 endpoints

min confidence0.70 0.50

No endpoints wrapped at confidence ≥ 0.70.

Parent server

ChiefLab

https://github.com/bdentech/chiefmo-agent

1/7 registries

View full server →