Minds: Synthetic Market Research

Export Mind Persona Profile

export_mind

Generates a branded profile for one existing Mind, identified by exact ID or name (partial names and typos resolve to the closest). Markdown is returned inline by default; PDF, DOCX, and PPTX artifacts are returned as base64 with a workspace link.

Input Schema

TableJSON 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

TableJSON 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

Behavior4/5

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

Annotations declare readOnlyHint=false with destructiveHint=false, consistent with generating artifacts. The description adds real behavioral context beyond that: markdown is returned inline by default, while PDF/DOCX/PPTX come back base64 with a workspace link, and fuzzy name resolution can select a different Mind than intended. It stops short of describing caching semantics or side effects of artifact generation.

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?

Two dense sentences, front-loaded with what the tool produces and the identification mode, then the output-format contract. Every clause carries information; nothing is padding.

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?

An output schema exists, so return values need not be explained, and the description still supplies the key output-format contract (inline markdown vs. base64 artifacts). With zero required parameters and full schema coverage, an agent has everything needed to invoke it correctly.

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 baseline is 3, and the schema already documents format, force, mindId, and mindName. However, the description adds meaning beyond the schema by clarifying that partial names and typos resolve to the closest match, which sharpens the fuzzy-matching semantics the schema only labels tersely.

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 specific verb (generates) and resource (branded profile for one Mind), and clearly separates this tool from siblings like export_audience, export_study, and export_heatmap by naming the Mind object as the target. It also specifies the identification method, so an agent can distinguish it without opening the schema.

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?

The description implies usage by explaining identifier handling and default vs. non-default formats, but never states when to choose export_mind over the sibling exports or when not to use it. Standard for a tool with 100% schema coverage, but no explicit routing guidance is given.

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.