get_briefing
Retrieve the project's analyzed Strategic Briefing: a prioritized read across monitored and researched areas showing what changed and what it means. Defaults to the hub digest.
Instructions
Get the current state of the project's Strategic Briefing — the prioritized analysis across 14 analysis areas: the 6 monitored dimensions it reads from your stored checks, plus 8 it researches for the briefing alone (landscape, funding, hiring, launches): what changed and what it means. This is the ANALYZED, as-of read, NOT raw monitoring — for live per-dimension data use the get__dashboard tools; for the competitor roster use list_competitors. Defaults to the 'hub' — a cheap digest (headline, top moves, per-dimension verdicts naming the section to open next) that answers most questions in one call. IMPORTANT — this returns the LATEST run in whatever state it is in. Check meta.status: on 'done' the briefing is in item; on 'running' it is being generated now (meta.progress gives the step; a run finishes within two hours — treat it as running until meta.status changes, never as late or failed for how long it has taken); on 'failed' the last attempt ended without producing an edition; on null the project has never had a briefing at all. On 'running' or 'failed', item is null but an earlier edition is usually still readable — call get_briefing_history and then get_briefing_edition. NEVER tell the user no briefing is available on the strength of a null item without checking get_briefing_history first. Only meta.status === null means the project has none. What the edition recommends doing is not in item: it is opened as tickets on the project's Strategic Tickets board. tickets says what this edition did to the board — opened, commented, alreadyOnBoard, recheckedUnchanged; a ticket in neither commented nor recheckedUnchanged was not measured by this edition. Counted as you read (byStatus: per column now), so a moved, edited or dismissed ticket reads from the board. Briefings are generated automatically, roughly 30 days after the last run.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| sections | No | Which briefing sections to return. Default ['hub'] — the executive digest that orients you and points to the deeper sections by name; this alone answers most questions in one cheap call. Add sections only when the question needs them: 'competitors' (the rival-by-rival read), any 'deep-<dimension>' for a full dimension dive (e.g. 'deep-ai-visibility', 'deep-pricing' — 14 available; the hub's verdicts tell you which one to open), or 'all' for the entire briefing (large — export/full-read only). The response's `contains` array lists exactly which sections that edition actually holds, in this same vocabulary — read it instead of guessing. What the edition recommends doing is in none of them: those recommendations are tickets on the project's board, and `tickets` on the response says what the edition did to the board. | |
| projectId | Yes | Project ID (from list_projects) | |
| includeCharts | No | Default false — each chart returns its title and note only, with NO underlying numbers, so do not answer a question about figures or a trend from a chart unless you set this. Set true to include the full series (time-series points, bar values); larger payload — use it only when you need the actual numbers. |