Chart Link Analysis

by amplitude96fc7d4c58bbNo license42 starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated today

Answers questions from an Amplitude chart or dashboard link — fetch the definition, pull the data, explain or adapt it. Use when the user pastes an Amplitude URL, asks "what does this chart show", wants a report refreshed from a dashboard, or wants to clone/adapt an existing analysis.

Instructions onlyData & Analytics
AI-generated overview

Reads an Amplitude chart or dashboard link, fetches its definition and data, and explains, refreshes or adapts the analysis.

What it does
Resolves an Amplitude URL to its entity type and IDs, then reads the chart or dashboard definition and pulls the underlying data. It can refresh a report at a chosen granularity, edit typed chart parameters to fork an analysis while keeping it linked to its parent, and render the result for the user to save. It also covers replicating a whole dashboard by rebuilding each chart.
When to use it
Use it when a user pastes an Amplitude chart, dashboard, experiment, notebook or cohort link and wants to know what it shows. It also fits requests to refresh a report from a dashboard or to clone and adapt an existing analysis.
Requirements
Requires access to Amplitude tooling: get_from_url, get_amplitude_charts, use_amp_dashboards, query_amplitude_data and render_amplitude_chart, plus valid Amplitude credentials and network access. It ships no scripts; saving a chart is done by the user in the widget.

Chart Link Analysis

Second most common job: the user pastes a link and wants the analysis understood, refreshed, or adapted.

The arc

  1. Resolve the URL. get_from_url returns the entity type, IDs, and (for charts) the current definition. One call handles chart, dashboard, experiment, notebook, and cohort links — use it instead of asking the user for IDs.
  2. Read the definition. For a chart: get_amplitude_charts with include: 'typed' — the typed params mirror the chart-builder UI and are the fastest way to see how the project spells events/properties. If typed fails to lower the chart ("advanced features are not modeled"), fall back to include: 'definition' for the raw form. For a dashboard: use_amp_dashboards action: 'get' (batch ≤3) to get its chart list, then read the charts that matter.
  3. Pull the data. get_amplitude_charts include: 'data' with the chart IDs, ≤3 IDs per call. For a report refresh, request the granularity the report needs (daily for week-over-week, weekly for monthlies).
  4. Adapt or fork. Edit the typed params, then call query_amplitude_data with the edited chart and chartId set to the saved chart's id — the parent's params fill gaps the typed model omits, and the edit stays linked to its parent. Render the result with render_amplitude_chart; the user saves it from the widget's Save chart button (there is no model-facing save tool). To replicate a whole dashboard in a new context: read the reference dashboard, then rebuild each chart — do not try to "copy" in one call.

Expectations to set

  • get_from_url does not run the chart — it returns metadata/definition. Data always comes from get_amplitude_charts include: 'data' (saved charts) or query_amplitude_data (ad hoc).
  • include: 'data' returns the same numbers the UI shows, including Amplitude's timezone bucketing — when comparing against external sources (e.g. BigQuery), call out timezone and partial-day differences explicitly.
  • Definition reads are cheap; data reads are the expensive calls. Read all definitions first, then decide which 1–3 charts actually need data.
  • Just need the link for the user? include: 'link' (the default) validates the ids and returns URLs without running anything.

Source and attribution

Source:amplitude/mcp-marketplaceinplugins/amplitude/skills/chart-link-analysisat commit96fc7d4

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal