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.

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/5.0

Behavior3/5

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

Annotations already provide readOnlyHint=false, destructiveHint=false, and idempotentHint=false. The description adds useful behavioral context: it uses the same renderer as the web app and returns binary artifacts as base64. However, it does not disclose any side effects like cache regeneration (mentioned only in the schema), nor does it state that validation reports require edit access. It neither contradicts annotations nor adds substantial behavioral richness beyond them.

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

Conciseness5/5

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

The description is three sentences with no fluff. The first sentence states the main purpose and the kind alternative; the second maps formats to kinds; the third notes base64 encoding. Every sentence earns its place, and the key information is efficiently front-loaded.

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?

Given the tool has an output schema and full schema parameter descriptions, the description covers the critical decision points: which kind to export, which formats are compatible, and how binary artifacts are returned. It does not repeat schema details like the edit-access requirement for validation reports, which is acceptable because the schema already provides it. Overall, an agent can invoke the tool correctly with the combination of description and schema.

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 description coverage is 100%, so the baseline is 3. The description goes beyond the schema by explicitly mapping allowed formats to each kind (PPTX only for brief, XLSX only for validation report), which is critical for format selection. It also clarifies the output return as base64, adding value for the format parameter and expected result handling.

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?

The description clearly states the specific verb 'Exports' and the resource: an Audience brief or its validation report. It also distinguishes between the two export kinds and, by naming 'Audience', inherently differentiates from sibling export tools like export_study or export_heatmap. The resource specificity is enough for an agent to select this tool correctly.

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

Usage Guidelines3/5

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

Usage is implied by the resource name: it exports audience-related content. However, the description does not explicitly state when to choose this tool over alternatives (e.g., no mention of 'use export_study for studies') nor does it outline prerequisites such as edit access for validation reports. It is not misleading, but the guidance is implicit rather than explicit.

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.