Ideally

Changes a section's title, body or both. Changes the narrative only, not an existing deck.

edit_narrative_section

Replaces one text field on a slide, by the name get_deck lists under text. For anything else (charts, layout, images, a rewrite) use revise_deck.

edit_slide_value

Replaces a slide's speaker notes with plain text, or clears them with an empty string. Nothing on the slide changes.

edit_speaker_notes

Generates a presentation deck from a narrative, once per narrative. Shape the sections and attach findings first. It takes 5 to 10 minutes: it returns the status and a handle for get_deck_status.

generate_deck

Gets one Canvas: its name, category, team, the markets it covers and its runs by date. Use the markets and run dates it lists for the other Canvas tools.

get_canvas

Lists a Canvas's questions in one market, a page at a time: each question's id, title, text, type and answer options. Use the ids for get_crosstab.

get_canvas_questions

Gets a study's TURF (market reach) results: how many people each option reaches on its own, and the best combinations of combinationSize options ranked by reach, with frequency and people reached. Exclusive options such as "None of the above" are left out, as the dashboard does.

get_turf

Gets the figures behind a finding search_findings returned, ready to chart: each question's series by audience, with bases, significance, the total and benchmarks. Draw the chart from these numbers as given.

get_chart_evidence

Crosstabs a Canvas's questions in one market by its segments, or by the answers to another question, a page of questions at a time: pass the same questionIds, by, byQuestionId, market and runDate with the NextCursor for the rest. Each question has its base (how many answered it), and each answer its share among all respondents (total) and, per column, the count, the column's base, the percentage, an index against the total (100 is the same as the total) and whether the difference is significantly higher or lower.

get_crosstab

Gets a narrative's deck as an outline: each slide's slotId, title, editable text fields, other content, speaker notes and cited findings, plus the checkpoints undo and restore_checkpoint move between. Address slides by slotId, never by number.

get_deck

Follows a revise_deck that was still working: returns the deck agent's reply once the revision is done.

get_revision_status

Says whether a narrative's deck is none, generating, ready or failed, and how long it has been generating. Follow up a generate_deck that was still running.

get_deck_status

Gets a Canvas's demand landscape in one market: its demand zones, largest first, each with its share of the market's occasions and the occasion-by-segment cells it is made of. Cells outside every zone are grouped last. It counts the Canvas's U&A studies and the studies shared with the Canvas's owner team, the same for every caller.

get_demand_landscape

Gets the data behind a study's driver chart for one open-ended question, one row per theme for all respondents or per concept. Each row gives the theme's impact on each metric with its p-value and whether it is significant (p below 0.05), how many responses mention the theme (as the dashboard counts them) and its sentiment. Impact is a regression coefficient in the metric's answer-scale points: how far a respondent's score moves when they mention the theme, other themes held constant; negative drags the metric down. Drivers are study-wide, never per segment. Themes whose absolute impact on every metric is below 0.05 are left out, strongest first. available is false when the driver model has not scored the question. Use it to chart, rank or compare drivers; use query_study_facts with driver_result to read them as written sentences.

get_drivers

Follows a create_finding that was still running: returns the finding once it is written, or the same handle while it is still running.

get_finding_status

Gets respondents' own words behind a finding search_findings returned, exactly as stored, with response ids. Never invent or paraphrase a quote. If the finding does not cover the audience, concept or theme asked about, search for one that does first.

get_finding_verbatims

Gets a narrative: its brief, and its sections in order with the findings each one cites. Address sections by id, never by position.

get_narrative

Summarises the ten most recent completed studies: framework, category, brand, markets, concepts and the questions the team wrote. For what one cost, use get_study_cost.

get_previous_studies_summary

Gets a study's price sensitivity (Van Westendorp) results: the optimal price, the indifference price, the acceptable range, and the curve of who finds each price too cheap, a bargain, getting expensive or too expensive.

get_price_sensitivity

Gets the research plan of each study: the background, what it set out to learn, its type, framework and audience. Read it once the studies are chosen, to frame the answer. A plan is intent, never evidence.

get_research_plans

Gets a Canvas's published Segmentation: each segment's name, the rules that put a respondent in it as readable text, and how many respondents it holds. A Canvas with no published Segmentation has no segments.

get_segments

Gets one study's plan: status, Canvas, framework, category, brand, background, objectives, dates, its schedule (start date, waves and weeks between them), marketReach (the market reach add-on with its maxOptionsSelect, left out when the study has none), and studyUrl, its link in the Ideally webapp.

get_study

Reads the study's builder conversation, oldest first: what the user, the study builder in the Ideally webapp and MCP clients said about the study. Each message says who it is from: user, webapp_builder or mcp. Read it before working on a study that already exists.

get_study_conversation

Gets what a study costs in credits: credits already charged and still to charge, per market, and the team's and organisation's credits left after those charges.

get_study_cost

Gets one study's survey design a page of questions at a time, in the order respondents see them, section by section: each question's type, answer options (an option with excludedFromBase true, such as a standard metric's "Not sure", is shown to respondents but its answers count in no base), the concept it belongs to, the block it sits in and its routing as readable text. Each page also carries the context blocks shown among its questions, and the first page lists the study's concepts and its splits with their blocks. Each question has two ids: studyQuestionId is its place in this study, which the results, driver and edit tools take; questionId is the question itself, shared by its copies when it is asked once per concept, and is what templates, Facts' keys.questionId and the raw data's question_id use.

get_study_design

Lists what a study's results can be cut by: the demographics (e.g. Gender, Generation), with each answer's id and how many respondents gave it, and the study's saved segments. Pass the answer ids as demographics, or a segment id as segment, to get_study_results, get_verbatims and the other results tools.

get_study_filters

Gets a study's results per concept, the way the dashboard shows them. A metric gives its top-two-box score and base (n) against the Ideally average norm, with the difference in points and whether it is significant, and against all respondents when a segment is chosen. Any other question gives each answer's share, count and base. Without studyQuestionId it covers the study's metrics; pass studyQuestionId for any other question.

get_study_results

Gets what respondents wrote to one open-ended question, a page at a time, with the concept each answer is about and the themes it was coded to. Later pages keep the first page's limit.

get_verbatims

Lists the Canvases this account can see, newest first, a page at a time.

list_canvases

Lists the audiences available to this account a page at a time: each one's category, whether it screens respondents to people active in that category, and the Canvases built on it. Narrow by category or words before paging through them all.

list_audiences

Lists the norms a study's metrics can be compared with in one market: Ideally, team, category and product type averages, medians and top 25%, each with its top-two-box score and roughly how many studies it rests on.

list_benchmarks

Lists the research frameworks a study can be built on, by study type, with what each is for, examples, and the standard questions it adds to every study on it. Recommend one from the brief before create_study. For a standard question's wording and scale, use list_standard_questions.

list_frameworks

Lists a study's narratives, newest first. A narrative is the story a presentation deck is built from. deck says whether it has a deck: none, generating or ready.

list_narratives

Lists the proposed edits on a study that nobody has accepted or rejected yet, oldest first. Each says who proposed it, mcp or webapp_builder (the study builder in the Ideally webapp), and its clientApp names the app, such as Claude Code.

list_pending_edits

Finds the saved question templates a study can reuse as they are, by section and words, a page at a time. Each says how many options it has; ask for the options, with each screener option marked as qualifying or screening out, with includeOptions.

list_question_templates

Lists the markets a study can run in, with their currency and default sample size.

list_regions

Lists the Ideally skills: guides for doing a task with these tools.

list_skills

Lists Ideally's standard questions: each one's wording, its answer scale in order, and the frameworks that add it. These are Ideally's scales, such as purchase intent, appeal and likeability: read one before writing or checking a question that should use it. positive marks the options a score counts; excludedFromScores marks a don't-know option. With a study, the wording and scales are the ones that study gets. A question some frameworks word differently is worded as the framework asked for, else the study's, else the first that adds it.

list_standard_questions

Lists the studies this account can see, most recently active first, a page at a time.

list_studies

Lists the teams under this account that the user can act in, with their role on each and whether they can create studies there. A study belongs to one team, so when there is more than one, ask the user which.

list_teams