Minds: Synthetic Market Research

Update Study, Audience or Mind

update_item

DestructiveIdempotent

Renames a Study or Audience or moves it into a folder. Renames a Mind, or records whether its facts come from real research data (mind.factsSource).

Input Schema

Name	Required	Description
`mind`	No	The Mind, when type is "mind", and where its facts come from (factsSource).
`name`	No	New name, 1 to 200 characters. Renaming does not change who can open the item. The person must be able to edit the item.
`type`	Yes	Kind of item: "study", "audience" or "mind".
`study`	No	The Study, when type is "study".
`folder`	No	Only when the person asks to file or move the item: the name (any case) or id of one of their folders. The item moves there and leaves their other personal folders; with no folder of that name, a personal folder is created.
`audience`	No	The Audience, when type is "audience".
`removeFromFolders`	No	true takes the item out of all the person's folders, only when they ask. Not with folder.
`confirmSharedFolder`	No	true only after the person confirmed in this conversation filing the item in a shared folder or taking it out of one, which changes who can open it.

Output Schema

Name	Required	Description
`id`	No	ID of the Study, Audience or Mind.
`url`	No	Minds workspace link for the item.
`name`	No	The name now saved, when it was renamed.
`type`	No	study, audience or mind.
`folder`	No	When folder was sent: the folder the item was filed in { id, name, created, otherMembers, pendingInvitations }; null after removeFromFolders.
`factsSource`	No	For a Mind, when factsSource was sent: where its facts now come from, generated or source_record.
`sharedFolders`	No	With confirmationRequired: the shared folders concerned { id, name, otherMembers, pendingInvitations }. After a move: the shared folders that still hold the item { id, name }.
`confirmationRequired`	No	True when nothing changed because filing the item in a shared folder, or taking it out of one, needs the person's confirmation.

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedNov 3, 2026

addedInput schema / properties / mind

Added value: +{
+  "description": "The Mind, when type is \"mind\", and where its facts come from (factsSource).",
+  "properties": {
+    "factsSource": {
+      "description": "Only for a Mind, only when the person says where its facts come from. \"source_record\": its facts were read from real research data (a survey respondent, an interview, a customer record); Minds then uses its saved instructions exactly as written and never checks, corrects or rewrites its facts or instructions on its own. \"generated\": Minds drafted the person and keeps its instructions consistent with its facts again. Only the Mind's owner or a workspace Owner or Admin can change it.",
+      "enum": [
+        "generated",
+        "source_record"
+      ],
+      "type": "string"
+    },
+    "id": {
+      "description": "Mind ID (UUID).",
+      "format": "uuid",
+      "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$",
+      "type": "string"
+    },
+    "name": {
+      "description": "Mind name, when the ID is not known.",
+      "minLength": 1,
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

changedInput schema / properties / type / description

Previous value: -"Kind of item: \"study\" or \"audience\"."New value: +"Kind of item: \"study\", \"audience\" or \"mind\"."

changedInput schema / properties / type / enum

Previous value: -[
-  "study",
-  "audience"
-]New value: +[
+  "study",
+  "audience",
+  "mind"
+]

addedOutput schema / properties / factsSource

Added value: +{
+  "description": "For a Mind, when factsSource was sent: where its facts now come from, generated or source_record.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

changedOutput schema / properties / id / description

Previous value: -"ID of the Study or Audience."New value: +"ID of the Study, Audience or Mind."

changedOutput schema / properties / type / description

Previous value: -"study or audience."New value: +"study, audience or mind."

AddedOct 26, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is largely known without the text. The description names the operations but adds no consequence information of its own — it does not say that moving an item out of personal folders or into a shared folder changes who can open it, nor does it mention the owner/admin permission constraint on factsSource; that detail lives only in the schema.

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 short sentences with the primary operation front-loaded and no filler. The second sentence's phrasing ('records whether its facts come from real research data') is slightly roundabout for what is effectively setting a factsSource flag, but it earns its place by flagging a non-rename operation.

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

Completeness3/5

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

For an 8-parameter mutation tool with nested objects and a destructive hint, the description accounts for renaming and factsSource but omits the folder-management half of the contract (folder vs. removeFromFolders exclusivity and the shared-folder confirmation path), which is exactly the part with destructive consequences. An output schema exists, so return values need not be described, and the 100% schema coverage mitigates the remaining gap.

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 every parameter including the nested id/name objects, folder, removeFromFolders and confirmSharedFolder is already fully documented in the schema. The description only echoes the mind.factsSource case, adding no syntax, defaults, or interaction rules beyond what the schema provides, so the baseline of 3 applies.

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

Purpose4/5

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

The description states concrete verbs (renames, moves, records) and concrete resources (Study, Audience, Mind, mind.factsSource), so the agent can tell exactly which items this generic-looking 'update_item' touches. It does not explicitly contrast itself with siblings such as set_sharing or update_study_template, but the operations listed are distinct enough that confusion is unlikely.

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 operation list — rename a Study/Audience/Mind, or move an item into a folder — but there is no explicit when-to-use/when-not-to-use guidance and no named alternative. Nothing warns the agent that folder moves or factsSource changes may need a separate confirmation or a different tool.

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.