Whole portfolio, ranked by urgency
portfolio_reportRuns maintenance checks across every site in a portfolio and returns one report ordered by urgency, showing downtime, expiring domains, and regressions. Use it to triage multi-site client lists.
Instructions
Runs the maintenance checks across every site in a portfolio and returns one report ordered by what needs action first: what is down, what expires soonest, what regressed since the last run.
Use it to answer "what needs attention this week?", "is anything down?" or "what do I put in this quarter's report?" across a whole client list. It is the right call whenever the question is about more than one site — running domain_check, ssl_check and uptime_check once per site by hand is what this replaces.
The portfolio comes from the "sites" argument, or from a local JSON file ("sites.json" by default) whose format is documented in sites.example.json. Pass "checks" to override what each site asks for — ["uptime"] answers "is anything down right now?" in a fraction of the time — and "tags" to report on part of the portfolio.
Do not use it to answer a question about one site: domain_check, ssl_check, uptime_check and seo_audit answer those directly and in a fraction of the time. It runs checks and reports; it never changes a site, and it never writes to the portfolio file.
A site that cannot be checked is reported as a finding, never as a failure of the whole report. Only a portfolio that cannot be read at all is an error.
What changed since the previous run is compared against one recorded snapshot. By default that snapshot lives in memory and is lost when this server restarts; a portfolio file may add a "history" path, and then the snapshot is written there and comparisons survive a restart for up to 90 days. Nothing is written unless the portfolio asks for it. Either way the report says what it had to compare against, and why it had nothing when it had nothing, rather than implying nothing changed. Only sites that both runs measured the same way are compared, so a quick uptime-only pass never invents regressions in the run after it.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| file | No | Path to a portfolio JSON file, e.g. "/Users/you/sites.json". Give the full path: a relative one is resolved against the directory this server was started in, which for a desktop client is usually "/" and not the user's own. Defaults to "sites.json". Ignored when "sites" is given. The format is documented in sites.example.json; only .json files can be read. | |
| tags | No | Only report on sites carrying at least one of these tags, e.g. ["retainer"]. Matched case-insensitively. Omit to report on the whole portfolio. | |
| sites | No | The portfolio, passed inline. Use this for a one-off report over a handful of sites. When omitted, the portfolio is read from the local file instead. | |
| checks | No | Run exactly these checks for every site, ignoring what the file says. Use it for a quick pass — ["uptime"] answers "is anything down right now?" in a fraction of the time. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| file | Yes | The file it was read from, when it was read from one. | |
| notes | Yes | Anything the report could not do, said plainly rather than left out. | |
| sites | Yes | Every site, most urgent first. | |
| source | Yes | Where the portfolio came from. | |
| changes | Yes | What changed since the previous run in this server process. | |
| summary | Yes | How many sites landed at each severity. | |
| severity | Yes | How much attention this needs. "critical" means act now; "warning" means act this month; "unknown" means the check could not establish the fact, which is not the same as it being fine. | |
| siteCount | Yes | How many sites the report covers, after any tag filter. | |
| generatedAt | Yes | When the report was produced, ISO 8601 in UTC. | |
| needsAttention | Yes | Everything worth acting on, worst first. This is the list the report exists to produce. |