Minds: Synthetic Market Research

Export Audience Brief

export_audience

Exports an Audience brief, or with kind "validation_report" the report of its validations (overall score calculation, every KPI, per-question answer shares, provenance), through the same renderer used by the web app. Brief: Markdown, PDF, DOCX, PPTX. Validation report: Markdown, PDF, DOCX, XLSX. Binary artifacts are returned as base64.

Input Schema

TableJSON Schema

Name	Required	Description
`kind`	No	What to export: "brief" (default), the Audience brief; or "validation_report", every scored validation of the Audience with the overall score calculation, every KPI with its 95% interval, per-question answer shares and provenance. A validation report needs edit access and a scored validation.
`force`	No	Regenerate instead of returning a cached artifact.
`format`	No	Export format: "md" (default), "pdf", "docx"; "pptx" for a brief only; "xlsx" (every table as a sheet) for a validation report only.
`audience`	No	Which Audience to export.

Output Schema

TableJSON Schema

Name	Required	Description
`format`	No	Export format.
`content`	No	Inline Markdown content, for Markdown exports.
`filename`	No	Suggested file name.
`mimeType`	No	MIME type of the file.
`audienceId`	No	Exported Audience.
`contentBase64`	No	Base64 file content, for binary formats.

Schema Changelog

Changes observed during successful MCP inspections.

Changed12 schema fields changedOct 2, 2026

removedOutput schema / properties / audienceId / anyOf

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

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

removedOutput schema / properties / content / anyOf

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

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

removedOutput schema / properties / contentBase64 / anyOf

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

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

removedOutput schema / properties / filename / anyOf

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

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

removedOutput schema / properties / format / anyOf

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

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

removedOutput schema / properties / mimeType / anyOf

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

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

Changed1 schema field changedSep 25, 2026

changedInput schema / properties / kind / description

Previous value: -"What to export: \"brief\" (default), the Audience brief; or \"validation_report\", every scored validation of the Audience with the overall score calculation, every KPI with its 95% interval and flat baseline, per-question answer shares and provenance. A validation report needs edit access and a scored validation."New value: +"What to export: \"brief\" (default), the Audience brief; or \"validation_report\", every scored validation of the Audience with the overall score calculation, every KPI with its 95% interval, per-question answer shares and provenance. A validation report needs edit access and a scored validation."

Changed3 schema fields changedSep 25, 2026

changedInput schema / properties / format / description

Previous value: -"Export format: \"md\" (default), \"pdf\", \"docx\", or \"pptx\""New value: +"Export format: \"md\" (default), \"pdf\", \"docx\"; \"pptx\" for a brief only; \"xlsx\" (every table as a sheet) for a validation report only."

changedInput schema / properties / format / enum

Previous value: -[
-  "md",
-  "markdown",
-  "pdf",
-  "docx",
-  "pptx"
-]New value: +[
+  "md",
+  "markdown",
+  "pdf",
+  "docx",
+  "pptx",
+  "xlsx"
+]

addedInput schema / properties / kind

Added value: +{
+  "description": "What to export: \"brief\" (default), the Audience brief; or \"validation_report\", every scored validation of the Audience with the overall score calculation, every KPI with its 95% interval and flat baseline, per-question answer shares and provenance. A validation report needs edit access and a scored validation.",
+  "enum": [
+    "brief",
+    "validation_report"
+  ],
+  "type": "string"
+}

Changed5 schema fields changedSep 22, 2026

addedInput schema / properties / audience

Added value: +{
+  "description": "Which Audience to export.",
+  "properties": {
+    "id": {
+      "description": "Audience ID (UUID).",
+      "type": "string"
+    },
+    "name": {
+      "description": "Audience name (fuzzy matched).",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

removedInput schema / properties / audienceId

Removed value: -{
-  "description": "Audience ID (UUID).",
-  "type": "string"
-}

removedInput schema / properties / audienceName

Removed value: -{
-  "description": "Audience name (fuzzy matched).",
-  "type": "string"
-}

removedInput schema / properties / groupId

Removed value: -{
-  "description": "Legacy alias for audienceId. Accepted for compatibility.",
-  "type": "string"
-}

removedInput schema / properties / groupName

Removed value: -{
-  "description": "Legacy alias for audienceName. Accepted for compatibility.",
-  "type": "string"
-}

Changed5 schema fields changedSep 22, 2026

addedOutput schema / properties / contentBase64

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Base64 file content, for binary formats."
+}

removedOutput schema / properties / downloadUrl

Removed value: -{
-  "description": "Download link for the exported file, when available."
-}

addedOutput schema / properties / filename

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Suggested file name."
+}

addedOutput schema / properties / format / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedOutput schema / properties / mimeType

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "MIME type of the file."
+}

Changed1 schema field changedSep 20, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "audienceId": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Exported Audience."
+    },
+    "content": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Inline Markdown content, for Markdown exports."
+    },
+    "downloadUrl": {
+      "description": "Download link for the exported file, when available."
+    },
+    "format": {
+      "description": "Export format."
+    }
+  },
+  "type": "object"
+}

AddedAug 27, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations declare readOnlyHint=false and idempotentHint=false, so the agent knows this produces a non-cached artifact without destroying data. The description adds genuinely useful context beyond that: caching behavior implied by force/regeneration, the base64 encoding of binary artifacts, and the edit-access requirement for validation reports.

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?

Two sentences, front-loaded with the core action and the kind branch before the format lists. The parenthetical enumeration of report contents is dense but earns its place by clarifying the second mode; there is minimal waste.

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

Completeness5/5

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

With an output schema present, the description needn't explain return values, and it still notes base64 encoding for binary output. Combined with annotations covering safety and the schema covering parameters, the definition leaves nothing an agent needs to call it correctly unaddressed.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents all four parameters including enums and the audience object. The description largely restates the kind/format matrix (Markdown/PDF/DOCX/PPTX vs Markdown/PDF/DOCX/XLSX) that the schema already covers, adding little new parameter meaning beyond the base64 return note.

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

Purpose5/5

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

Specific verb (Exports) plus resource (Audience brief) with two clearly enumerated modes (brief vs validation_report), each detailing what is included. This distinguishes it from the sibling export_heatmap/export_mind/export_study tools, which export different artifacts.

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

Usage Guidelines4/5

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

The description branches clearly by kind and states format constraints per kind (PPTX brief-only, XLSX report-only), and the schema notes that a validation report needs edit access and a scored validation. However it never states an explicit when-not or names an alternative tool, so the routing guidance is implicit rather than complete.

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.