share_dashboard
Make one of the user's saved dashboards PUBLIC at an unguessable URL — or revoke that link with revoke: true. Anyone with the link sees the dashboard's LIVE warehouse data with no sign-in, served from a shared server-side cache so viewers cannot run up query costs. Only call this when the user has explicitly asked to share or publish the dashboard, and quote their words in user_request — the tool refuses otherwise, exactly like share_artifact. Idempotent: sharing twice returns the same URL. Revoking kills the link permanently; sharing again afterwards mints a NEW URL. The returned page accepts ?marquee=1 (chrome-free, for wall displays), &refresh=<seconds> (auto-refresh, min 30), and &panel=<n> (single panel). A request to host it on a search-friendly or SEO link counts as asking to share; once an admin lists it for search it is also served at the readable /nem/<slug> (see the dashboard guide). For a one-off analysis write-up use share_artifact instead — this is for a live page someone returns to.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"name": "<name>",
"user_request": "<user_request>"
},
"name": "share_dashboard"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Which dashboard, as its name or title. | |
| revoke | No | Pass `true` to REVOKE the public link instead of creating one. The link dies immediately and permanently — sharing again later mints a NEW URL, so anyone holding the old one stays locked out. | |
| question_id | No | Optional UUID returned by an earlier `start_question` call. When provided, this tool call is attributed to that question. | |
| user_request | Yes | REQUIRED. The user's own words asking for this dashboard to be made public (or private again), quoted verbatim — e.g. "share my price dashboard", "make it public", "host it on an SEO-friendly link", "kill the public link". Sharing puts live warehouse data behind a URL anyone can open with no sign-in. That is not something to infer — if you cannot point at words asking for it, ask the user first and tell them what public means here. |