Minds: Synthetic Market Research

Export Mind Persona Profile

export_mind

Generates a branded profile for one existing Mind, identified by exact ID or the best fuzzy name match among the newest 1,000 Minds. 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.

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

Behavior4/5

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

Annotations are all false and thus convey no behavioral claims, so the description carries the burden. It discloses meaningful behavioral details: the selection scope (newest 1,000 Minds), the default inline Markdown return, and that PDF/DOCX/PPTX are returned as base64 with a workspace link. It stops short of mentioning side effects, auth, or rate limits, but for an export operation this is reasonably transparent.

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 sentences, both information-dense and front-loaded. The first sentence covers purpose and selection; the second covers output formats and delivery. There is no repetition or filler, and the description earns its place.

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 that a full output schema exists and parameter descriptions cover all four parameters, the description is adequately complete. It explains the core call behavior and selection semantics. It does not cover error conditions or prerequisites, but those are not essential for an export tool with this level of schema support.

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 adds value beyond the schema by explaining that fuzzy matching applies to the newest 1,000 Minds and clarifying that Markdown is returned inline by default, which reinforces and slightly extends the format parameter semantics. It does not cover the force parameter, but that parameter's own schema description is sufficient.

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 ('Mind persona profile'), and scopes it to 'one existing Mind' with exact ID or fuzzy name match among the newest 1,000 Minds. This clearly distinguishes it from sibling export tools like export_audience, export_study, and export_heatmap, which target different resource types.

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 provides clear context on when to use the tool (to export a Mind persona profile) and describes the primary selection modes (exact ID vs fuzzy name). However, it does not explicitly exclude alternatives or state when not to use this tool in favor of a sibling, so it misses the highest bar for explicit usage routing.

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.