Search for Claude prompts for Looker Studio and you'll find long copy-paste lists. Most of them share one problem: on its own, Claude can't see your Looker Studio dashboard, so a prompt like "summarize last month's search traffic" has nothing to read. A prompt only works when Claude has a tool that can reach the data.
That's what the Slideform MCP server is for. Once your Looker Studio dashboard is connected to Slideform, Claude can see its charts, run the report you've built on it, and hand back a finished Google Slides deck.
We ran every prompt below on October 30, 2026, in a Claude session connected to the hosted Slideform MCP server. The account had a Google Search Console dashboard in Looker Studio connected to Slideform, plus a Slideform project that turns it into a monthly report. Under each prompt you'll find the tool Claude called and what actually came back. Your project names and numbers will differ, but the shape of each answer won't.
New to the Looker Studio integration? Start with How to Embed Looker Studio in Google Slides. It walks through connecting the dashboard and building the kind of template these prompts run.
Before you start: connect Claude to Slideform
You need three things in place:
- Your Looker Studio dashboard, connected to Slideform. In Looker Studio, share the report with
share@slideform.coand turn on embedding (File > Embed report > Enable embedding), then add it as a data source in Slideform. - A Slideform project built on that dashboard. This is the slide template whose placeholders are mapped to the dashboard's charts, scorecards, and tables.
- The Slideform MCP server, added to Claude. All it needs is a Slideform API token. The one-line command for Claude Code, the Claude Desktop install bundle, and the settings for other MCP clients are on the MCP page.
10 tested Claude prompts for Looker Studio reports
1. Find the report you want to run
Which Slideform projects can I run?
Tool: list_projects
What came back: Every runnable project in the account, by name and id. There were 14 in our case, including the Search Console Report project built on the Looker Studio dashboard. Claude carries the id from this answer into the prompts that follow, so you never have to copy one yourself.
2. See which Looker Studio charts Slideform can use
Which of my data sources is a Looker Studio dashboard, and what charts and scorecards are on it?
Tools: list_data_sources, then describe_data_source
What came back: Claude picked out the one Looker Studio source from a list that also held Google Sheets, BigQuery, Tableau, and Salesforce sources. Then it listed the dashboard's elements: an Impressions over Time chart, a Country Impressions bar chart, a Query Details table, Impressions, Clicks, and Site CTR scorecards, and an image of the whole page. It also listed the dashboard's own filters (Date Range, Device Category, and Country) with every allowed value.
3. Check what a report needs before you run it
What inputs does the Search Console Report need before I run it?
Tool: describe_project
What came back: Each input with its type, label, and default. The reporting period was marked required and had no default. A country input defaulted to United States. The response also flagged that one dropdown couldn't load its values from the data source and needed to be re-mapped, which is better to learn before a run than after.
This prompt matters more than it looks. Slideform doesn't reject a run that's missing an input; it leaves that spot on the slide blank. Ask Claude to check the inputs first and to ask you for anything required.
4. Run the report for a specific period
Run the Search Console Report for September 2026 in the United States, compared with August.
Tool: run_project
What came back: A job id right away, with the status "submitted". Claude turned "September 2026" into the date range the project expects (2026-09-01 to 2026-09-30) and set the comparison period to August. Runs are asynchronous on purpose, so a long report can't time out your chat.
5. Get the finished deck
Is that report done? Send me the link.
Tools: list_jobs, then download_result
What came back: The job was already marked "completed" a few seconds after it was submitted, and download_result returned a link to the new Google Slides deck, named for the country and date. This project saves to Google Slides, so the result was a link. A project that produces a file, such as a PowerPoint deck, returns the file instead.
6. Confirm nothing came back blank
Did anything go wrong in that run? Check for blank slides or failed charts.
Tool: get_job_errors
What came back: Zero errors: no failed data fetches and no unresolved placeholders. It takes seconds, and it's worth doing before you forward a deck to a client.
7. Find out why a scheduled report came back partial
The scheduled Search Console Report from October 1 looks incomplete. What went wrong?
Tools: list_project_downloads, then get_job_errors
What came back: Claude found the October 1 scheduled run, marked "partial", and pulled its errors. All eight pointed to slide 4. Three placeholders on that slide (a data table, a bar chart, and an AI-written summary) had no data assigned, and the AI summary had also failed to fetch because a model API key it relied on wasn't set up. Every error names the slide, the placeholder, and the data source, so you know exactly what to fix.
8. Reuse a saved insight built on Looker Studio data
Do I have any saved insights built on my Looker Studio impressions data?
Tool: list_insights
What came back: One match: a saved line chart based on the dashboard's Impressions over Time chart and its underlying table. It was marked to re-run from a cached script without a new model call, and it came with a ready-made binding for placing it in a project.
9. Ask how to set something up
How do I connect a Looker Studio dashboard to Slideform?
Tool: search_slideform_docs
What came back: The matching section of the Slideform manual: share the dashboard with share@slideform.co and enable embedding. It added a useful tip. Slideform indexes Looker Studio one page at a time, so a dashboard with fewer pages indexes faster. By default this search doesn't use AI and doesn't bill the account.
10. Check your remaining usage
How many slide updates do I have left this month?
Tool: get_usage
What came back: The account's plan, with used, limit, and remaining counts for both slide updates and AI insight tokens. It's worth asking before you run a big batch of reports.
What Claude and Slideform can't do with Looker Studio
Most prompt lists skip this part. Here's what to expect:
- Claude doesn't connect to Looker Studio directly. Claude talks to Slideform, and Slideform reads the dashboard you've shared with it. Sharing the report and turning on embedding happen in Looker Studio, not in the chat.
- It works with what's already on the dashboard. Claude can use the charts, scorecards, and tables on the pages Slideform has indexed. It can't edit your Looker Studio report or add a chart to it.
- Missing inputs aren't refused. A run that leaves out a required input still completes, with that spot blank.
run_projectlists any required inputs you skipped, and prompt 3 catches them before the run. - Some actions need an Editor or Admin role. Every call runs as the owner of the API token. Editing projects, changing how placeholders map to data, and bulk runs (one report per client from a single request) need Editor or Admin access.
- AI-powered tools bill your account, and only run when you allow them. Turning a finished deck into a template, auto-mapping placeholders to dashboard metrics, and creating new insights all run an AI model. Those tools refuse to run unless the request sets
allow_ai=true, so Claude has to opt in explicitly. Ordinary runs count against your plan's monthly slide updates, which prompt 10 shows. - Reports aren't instant. A run returns a job id first, and Claude checks back for the result. If a response ever gets lost, ask Claude to check recent jobs before running the report again, instead of starting a duplicate.
Frequently asked questions
Can Claude read my Looker Studio dashboard?
Not on its own. With the Slideform MCP server connected, Claude can see the charts, scorecards, tables, and filters Slideform has indexed from your dashboard, and run the reports you've built on them.
Does this work in Claude Desktop and Claude Code?
Yes. Claude Code connects to the hosted server with one command, and Claude Desktop installs it from a one-click bundle. Other MCP clients that support streamable HTTP can connect too. Setup for each is on the MCP page.
Can I get PowerPoint instead of Google Slides?
Yes. The output format is set on the Slideform project, so the same prompts work for either. See Integrate Looker Studio with PowerPoint.
Does Claude see my Google credentials?
No. The MCP server only carries your Slideform API token. Your data source connections stay inside Slideform, under the same access rules your team already uses.
Do I have to use Claude to run these reports?
No. Claude is one more way to press Generate. The same project runs from the Slideform app or on a schedule. For the full workflow, see Use AI to connect Looker Studio to Google Slides, or Embed Looker Studio Metrics in Slides as Text for scorecards and KPIs.
Final takeaway
A prompt list is only as good as the tools behind it. Connect your Looker Studio dashboard and template to Slideform once, and these prompts can find, run, check, and deliver your reports from a Claude chat.
Put your Looker Studio reports one prompt away
Get full access to Slideform with a free trial. No credit card required.