Command
Use list_projects({}) to confirm my supplied project host is visible. Use my chosen days value of 7, 30, or 90 for every time-windowed call. Use my supplied market-to-project mapping and priority thresholds to select visible hosts. Read get_overview({host, days}), get_brand_insights({host, days}), and get_gap_analysis({host, days}) for each. Produce a market matrix showing available metrics, returned leading competitors, coverage notes, and threshold exceptions. Rank priorities only among comparable projects, keeping missing values unknown. Explain whether apparent weakness may reflect language or prompt differences. Draft a regional review agenda; market labels come from my mapping, not automatic geographic segmentation. Return evidence links, coverage limits, and explicit unknowns; never infer unsupported scores.What you need
- A market-to-visible-project mapping, supported window, and explicit priority thresholds.
- Coverage and language notes for each project; saved exports for any historical comparison.
Build a transparent market matrix
Collect the same available observations across your mapped projects and place coverage notes beside every market. Use returned competitor details only where available, and explain which projects can be compared fairly before using thresholds to identify potential weaknesses or priorities for regional teams.
Turn a rollup into a review agenda
Summarize the markets that need closer review, the leading competitor evidence available, and the next question for each regional owner. Keep unknowns and mismatched coverage visible so the rollup supports a focused discussion without inventing country scores or automatic geographic analytics.