Minds: Synthetic Market Research

Export Study Results

export_study

Destructive

Queues Study results export: executive/full reports in PDF/DOCX/PPTX/Markdown; raw CSV/XLS/SPSS SAV. Returns job/artifact status. Full reports can fetch public HTTPS portraits. force can replace artifacts. Completed exports can irreversibly email the requesting account.

Input Schema

Name	Required	Description
`kind`	No	Report kind. Defaults to full_report, except CSV/XLS/SAV which default to raw_data.
`force`	No	Regenerate instead of returning a cached artifact.
`study`	No	Which Study to export. Omit entirely to use the active Study from this MCP session.
`format`	No	Export format: "pdf" (default), "docx", "pptx", "csv", "xls", "sav", or "md" (also accepts "markdown"). Executive-summary and full-report PPTX exports use a slide-native 16:9 layout.
`length`	No	Requested report detail for executive_brief and full_report exports.
`scheduledRunId`	No	Export only the messages produced by one scheduled run of this Study, instead of the whole timeline. Use the run ID from the Study schedule history.
`researchResultId`	No	Export only the selected Research Result. Use its saved user-origin message ID from this Study. Omit for a whole-Study export.

Output Schema

Name	Required	Description
`kind`	No	Export kind.
`jobId`	No	Asynchronous export job; poll it with get_study_status.
`format`	No	Export format.
`status`	No	Export job status.
`studyId`	No	Exported Study.
`downloadUrl`	No	Download link, once the export is ready.
`workspaceUrl`	No	Minds workspace link for the Study.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 5, 2026

addedInput schema / properties / researchResultId

Added value: +{
+  "description": "Export only the selected Research Result. Use its saved user-origin message ID from this Study. Omit for a whole-Study export.",
+  "minLength": 1,
+  "type": "string"
+}

Changed4 schema fields changedOct 21, 2026

changedInput schema / properties / study / properties / id / description

Previous value: -"Study ID (UUID). Omit with studyName to export the active Study."New value: +"Study ID (UUID). Omit id and name to export the active Study."

addedInput schema / properties / study / properties / id / format
```
Added value: +"uuid"
```

addedInput schema / properties / study / properties / id / pattern

Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"

changedInput schema / properties / study / properties / name / description

Previous value: -"Study name (exact or partial, case-insensitive; fuzzy fallback for typos). Omit with studyId to export the active Study."New value: +"Study name (exact or partial, case-insensitive; fuzzy fallback for typos). Omit id and name to export the active Study."

Changed1 schema field changedOct 7, 2026

changedInput schema / properties / study / properties / name / description

Previous value: -"Study name (fuzzy matched among the newest 1,000 visible Studies; use studyId for older records). Omit with studyId to export the active Study."New value: +"Study name (exact or partial, case-insensitive; fuzzy fallback for typos). Omit with studyId to export the active Study."

Changed4 schema fields changedOct 2, 2026

removedOutput schema / properties / studyId / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / studyId / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / workspaceUrl / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / workspaceUrl / type
```
Added value: +[
+  "string",
+  "null"
+]
```

Changed5 schema fields changedSep 22, 2026

removedInput schema / properties / panelId

Removed value: -{
-  "description": "Study ID (UUID; legacy wire field name: panelId). Omit both panelId and panelName only when exporting the active Study from this MCP session.",
-  "type": "string"
-}

removedInput schema / properties / panelName

Removed value: -{
-  "description": "Study name (fuzzy matched; legacy wire field name: panelName). Omit both panelName and panelId only when exporting the active Study from this MCP session.",
-  "type": "string"
-}

addedInput schema / properties / study

Added value: +{
+  "description": "Which Study to export. Omit entirely to use the active Study from this MCP session.",
+  "properties": {
+    "id": {
+      "description": "Study ID (UUID). Omit with studyName to export the active Study.",
+      "type": "string"
+    },
+    "name": {
+      "description": "Study name (fuzzy matched among the newest 1,000 visible Studies; use studyId for older records). Omit with studyId to export the active Study.",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

removedInput schema / properties / studyId

Removed value: -{
-  "description": "Study ID (UUID). Omit with studyName to export the active Study.",
-  "type": "string"
-}

removedInput schema / properties / studyName

Removed value: -{
-  "description": "Study name (fuzzy matched among the newest 1,000 visible Studies; use studyId for older records). Omit with studyId to export the active Study.",
-  "type": "string"
-}

Changed1 schema field changedSep 22, 2026

changedInput schema / properties / studyName / description

Previous value: -"Study name (fuzzy matched). Omit with studyId to export the active Study."New value: +"Study name (fuzzy matched among the newest 1,000 visible Studies; use studyId for older records). Omit with studyId to export the active Study."

Changed1 schema field changedSep 20, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "downloadUrl": {
+      "description": "Download link, once the export is ready."
+    },
+    "format": {
+      "description": "Export format."
+    },
+    "jobId": {
+      "description": "Asynchronous export job; poll it with get_study_status."
+    },
+    "kind": {
+      "description": "Export kind."
+    },
+    "status": {
+      "description": "Export job status."
+    },
+    "studyId": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Exported Study."
+    },
+    "workspaceUrl": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Minds workspace link for the Study."
+    }
+  },
+  "type": "object"
+}

Changed2 schema fields changedSep 4, 2026

changedInput schema / properties / format / description

Previous value: -"Export format: \"pdf\" (default), \"html\" or \"png\" for executive summaries, \"docx\", \"pptx\", \"csv\", \"xls\", \"sav\", or \"md\" (also accepts \"markdown\"). Executive-summary PPTX exports use a slide-native 16:9 layout."New value: +"Export format: \"pdf\" (default), \"docx\", \"pptx\", \"csv\", \"xls\", \"sav\", or \"md\" (also accepts \"markdown\"). Executive-summary and full-report PPTX exports use a slide-native 16:9 layout."

changedInput schema / properties / format / enum

Previous value: -[
-  "pdf",
-  "html",
-  "png",
-  "docx",
-  "pptx",
-  "csv",
-  "xls",
-  "sav",
-  "md",
-  "markdown"
-]New value: +[
+  "pdf",
+  "docx",
+  "pptx",
+  "csv",
+  "xls",
+  "sav",
+  "md",
+  "markdown"
+]

AddedAug 27, 2026

TDQS

A3.6/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the destructive/openWorld annotations it discloses genuinely new behavior: the export is queued asynchronously, it returns job/artifact status, full reports can fetch external public HTTPS portraits, and completed exports can irreversibly email the requesting account. The email side effect is a real consequence not captured by any annotation, which is exactly what the description should add.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Semicolon-separated clauses front-load the purpose and then layer formats, return behavior, and side effects with no filler. The telegraphic phrasing ("raw CSV/XLS/SPSS SAV") is compact but slightly compressed for the format list.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, it needn't document return shapes, yet it still flags job/artifact status, and it warns about the destructive force flag and irreversible emailing for a mutation tool. The main remaining gap is routing among the many export/render siblings.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds cross-parameter meaning the schema does not: which formats pair with which report kinds (executive/full vs raw data), and that force replaces existing artifacts. It does not cover the scheduledRunId or researchResultId scoping here, but those are well documented in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Queues Study results export" gives a specific verb plus resource, and the format/kinds enumeration (executive/full reports vs raw CSV/XLS/SAV) makes the output space concrete. It never names a sibling, so an agent must still infer the boundary with render_study_results or export_audience.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description says what the tool produces but never states when to choose it over alternatives such as render_study_results or export_heatmap, nor any prerequisites. The only selection logic (kind defaults, omitting study to use the active Study) lives in the schema, not in the description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Minds: Synthetic Market Research tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.