Build Charts with Typed Params

Builds Amplitude charts using the typed `chart` parameter on query_amplitude_data — events, filters, group-bys, segments, date ranges, and per-kind fields for segmentation, funnel, retention, sessions, and data tables. Use when creating a chart, modifying or forking a saved one, or when a query returns empty data.

48 stars 12 forksData & Analytics Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add amplitude/mcp-marketplace

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add amplitude/mcp-marketplace --skill build-charts-with-typed-params
Manual install
git clone --depth 1 https://github.com/amplitude/mcp-marketplace.git /tmp/mcp-marketplace
mkdir -p ~/.claude/skills
cp -r /tmp/mcp-marketplace/plugins/amplitude/skills/build-charts-with-typed-params ~/.claude/skills/build-charts-with-typed-params

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Build Charts With Typed Params

Express the chart as typed, UI-shaped parameters and let the server compile it.
Do not hand-build raw definition JSON.

## Typed `chart` first

`query_amplitude_data` takes **exactly one of** `chart` or `definition`.

- **`chart` (preferred)** — a small model mirroring the chart builder UI. It is
  compiled server-side by Langley's `CompileChart` into a validated definition,
  so a successful compile is structurally correct by construction. Compile
  errors name the offending field and come back with a fix-oriented hint.
- **`definition` (fallback)** — raw definition JSON. Only for chart types the
  typed model does not cover (`composition`, `revenueLtv`) or advanced params
  with no typed field.

Field names are snake_case; they are validated server-side by Pydantic.

## The one thing that goes wrong

The compiler validates **structure**, not your taxonomy. An event or property
name that doesn't exist won't error — it returns a well-formed chart with
**empty data**, which reads like a real answer of "zero".

Resolve names first with the taxonomy search/read capabilities advertised by
the connected catalog. Read event, user, or group properties as appropriate
and use the exact name **and scope** returned. Do not invent a property-reader
name from server prose or copy parameters from an older schema.

## Two workflows

**Create:** discover names with the current taxonomy capability → build the typed `chart` → call
Read the full skill on GitHub

Details

Skill name
build-charts-with-typed-params
Path
plugins/amplitude/skills/build-charts-with-typed-params/SKILL.md
License
MIT
Repo updated
17 November 2026

FAQ

What does the Build Charts with Typed Params skill do?

Builds Amplitude charts using the typed `chart` parameter on query_amplitude_data — events, filters, group-bys, segments, date ranges, and per-kind fields for segmentation, funnel, retention, sessions, and data tables. Use when creating a chart, modifying or forking a saved one, or when a query returns empty data.

How do I install the Build Charts with Typed Params skill?

Claude Code plugin: /plugin marketplace add amplitude/mcp-marketplace. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Build Charts with Typed Params popular?

It lives in amplitude/mcp-marketplace, which has 48 GitHub stars and 12 forks.

Related skills

Add Analytics Instrumentation

48

amplitude/mcp-marketplace

End-to-end analytics instrumentation workflow for a PR, branch, file, directory, or feature. Reads the code, discovers what events should be tracked, and produces a concrete instrumentation plan — all in one shot. Use this skill whenever a user wants to add analytics to a PR, asks "instrument this PR", "add tracking to this branch", "what analytics does this file need", "instrument the checkout flow", "run the full instrumentation workflow", or any request that implies going from code changes to a tracking plan. Also trigger when the user gives you a PR link, branch name, file path, or feature

Data & Analytics12

Analyze Account Health

48

amplitude/mcp-marketplace

Summarizes B2B account health by analyzing usage patterns, engagement trends, risk signals, and expansion opportunities. Use for customer success reviews, renewal preparation, QBRs, or account prioritization.

Marketing, Sales & Business12

Analyze AI Topics

48

amplitude/mcp-marketplace

Analyzes what users ask AI agents about and how well each topic is served. Only use when the user has Amplitude Agent Analytics instrumented in their project. Use when the user asks "what are people asking the AI", "top AI topics", "where is the AI struggling", "AI coverage gaps", "what should we improve in our AI", or wants product insights from AI conversation patterns.

AI, LLMs & Agents12

Chart Link Analysis

48

amplitude/mcp-marketplace

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.

Data & Analytics12

Analyze Dashboard

48

amplitude/mcp-marketplace

Deeply analyze Amplitude dashboards by analyzing key charts, surfacing top areas for concern and takeaways, identify anomalies, then explain changes using customer feedback trends

Data & Analytics12

Create Chart

48

amplitude/mcp-marketplace

Creates Amplitude charts from natural language descriptions, handling event selection, filters, groupings, and visualization choices. Use when you know what you want to measure but prefer not to build the chart manually.

Data & Analytics12

Browse the most popular Claude skills, all data & analytics skills, or write your own with the skills generator.