DashThis

Pull a dashboard's current values so you can help the user make sense of them and communicate them to their client. Use when: the user wants the actual numbers on a dashboard — to summarize performance, spot what moved, or draft an update for a client or stakeholder. Returns: per widget, its title, kind and read status. A data widget carries its metric columns and current-period rows (dimension values + one raw value per metric), plus the matching comparison-period rows when compareTo is set. A widget whose content can't be read here comes back status=unsupported or status=failed with a reason — the dashboard may still display it, so don't report it as empty. A text widget carries the text written on it as content, as HTML — often the user's own commentary about the numbers, with contentPeriodEndDate saying which period it was written for. Values are read over the dashboard's own period unless you ask for another one, and the response says which window answered — name that window whenever you report the numbers. Rules: values are raw as the widget returns them, so compute deltas and format for the reader yourself, and never state a metric or number the widget didn't return. Then: turn the numbers into the story the user needs — what changed and why it matters to their client — and offer to draft the update in whatever tool they use.

get_dashboard_data

Lists the dashboards in the user's account so you can find one or scan across clients. Use when: the user wants an overview of their dashboards, asks "what dashboards do I have", or is about to work on a specific dashboard's report. Returns: a page of dashboards — each with id, title, group, View-mode URL, creator, and creation date (data sources only when includeSources is set) — plus the total count and paging info. No client entity exists — infer client grouping from group and names. Filter server-side to keep results small and targeted: titleContains, integration, hasSourceError. Page with offset/limit. Turn on includeSources only when the user cares about a dashboard's data sources — it makes the response much larger. Then: offer the useful next move in the user's own words — open a dashboard's report, prep a client recap, reconnect a source in error, or share a View URL — one step at a time. Read-only.

list_dashboards

Report back to the DashThis team when these tools can't do what the user needs, or when the user asks you to pass something on. Use when: the user wants something no tool here does (creating or editing a dashboard, sending a report, alerts — anything beyond reading); a tool kept failing or was refused; the values you got back clearly weren't what they asked about; getting there took a lot of guessing; or the user says outright that something is wrong, missing, or good. Returns: a reference for the report when it was recorded and none when it wasn't, plus the help center and support ticket links to hand the user. Rules: once per problem, not once per turn. Write summary in your own words — what they were trying to do and what stopped them — and keep names, email addresses and anything resembling a key out of it. Logging a report is not a fix and nobody replies to it; the ticket link is what reaches a person. Then: tell the user plainly what you couldn't do, give them the link that fits, and offer the nearest useful thing you can do instead. Say it's been logged only when this call hands back a reference, and quote that reference — no reference means no report, whatever you meant to do.

provide_feedback

Confirms which DashThis account this session is acting on. Returns the account resolved from the access token, its company name, status, and dashboard count.

whoami