Minds: Synthetic Market Research

Export Mind Persona Profile

export_mind

Destructive

Exports an existing Mind by ID/name: inline Markdown by default, or PDF/DOCX/PPTX. PDF/PPTX can fetch public HTTPS portraits. Starts artifact work; force can replace an artifact. Slow exports may irreversibly email the requesting account when ready.

Input Schema

Name	Required	Description
`force`	No	Regenerate instead of returning a cached artifact.
`format`	No	Export format: "md" (default) markdown persona profile (returned inline), "pdf" portrait branded profile, "docx" Word document, "pptx" editable branded deck
`mindId`	No	Mind ID (UUID)
`mindName`	No	Mind name (fuzzy matched)

Output Schema

Name	Required	Description
`format`	No	Export format.
`mindId`	No	Exported Mind.
`content`	No	Inline Markdown content, for Markdown exports.
`mindUrl`	No	Minds workspace link for the Mind.
`filename`	No	Suggested file name.
`mimeType`	No	MIME type of the file.
`contentBase64`	No	Base64 file content, for binary formats.

Schema Changelog

Changes observed during successful MCP inspections.

Changed14 schema fields changedOct 2, 2026

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"
+]
```

removedOutput schema / properties / mindId / anyOf

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

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

removedOutput schema / properties / mindUrl / anyOf

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

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

Changed2 schema fields changedSep 22, 2026

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

addedInput schema / properties / mindId / pattern

Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"

Changed1 schema field changedSep 20, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "content": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Inline Markdown content, for Markdown exports."
+    },
+    "contentBase64": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Base64 file content, for binary formats."
+    },
+    "filename": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Suggested file name."
+    },
+    "format": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Export format."
+    },
+    "mimeType": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "MIME type of the file."
+    },
+    "mindId": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Exported Mind."
+    },
+    "mindUrl": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Minds workspace link for the Mind."
+    }
+  },
+  "type": "object"
+}

Changed1 schema field changedAug 25, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
AddedAug 10, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Beyond the annotations it discloses that the call starts asynchronous artifact work, that `force` can destructively replace an artifact, that portrait fetching for PDF/PPTX makes public HTTPS requests, and that slow exports may irreversibly email the requesting account — non-obvious side effects that align with and enrich destructiveHint/openWorldHint rather than repeating them.

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?

Front-loaded with purpose and format options, and every sentence carries information, though the telegraphic phrasing ("Starts artifact work") costs some clarity that a few more words would fix.

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 covering return values and full parameter descriptions, the description covers the key risk surface — destructive replacement, async completion, and emailing. It omits prerequisites such as what happens when the name does not match or whether a Mind must be shared first.

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 coverage is 100%, so the baseline is 3; the description adds only light meaning (md is returned inline, portraits apply only to PDF/PPTX, force replaces rather than reuses a cached artifact) and leaves the mindId/mindName relationship unexplained.

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 states a concrete verb and resource ("Exports an existing Mind by ID/name") and enumerates the output modes (inline Markdown default, PDF/DOCX/PPTX), which is enough to distinguish it from the audience/study/heatmap export siblings without opening a schema.

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?

It establishes the default behavior (inline Markdown unless a format is requested) and when `force` is relevant (replacing an existing artifact), but never states when to prefer this over export_audience/export_study, nor the mindId vs mindName selection rule beyond "ID/name".

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.