Minds: Synthetic Market Research

List Studies

list_studies

Read-onlyIdempotent

Lists the authenticated user's Studies, most recently updated first, one page at a time: limit (default 20) and offset, with nextOffset to continue. Each row carries the Study's Audiences with their Mind counts, stored message count, sharing state and links. searchQuery returns the best fuzzy name match instead of a page.

A Study is the persistent workspace holding its Audiences, questions, multi-question blocks, results, exports and history. Its Minds and per-question results come from the Study status rather than this listing. Study deletion is not available here.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Studies per page, newest first (default 20, max 100).
`offset`	No	Number of Studies to skip; pass nextOffset from the previous page to continue.
`searchQuery`	No	Search for a Study by name (fuzzy matching supported). Returns the best match.

Output Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Page size used.
`offset`	No	Offset of this page.
`studies`	No	Studies: id, name, question count, dates, sharing state, Audiences with Mind counts, and links.
`nextOffset`	No	Offset of the next page; absent on the last page.
`shownCount`	No	Number of items in this response.
`totalCount`	No	Total number of items available.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 20, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "limit": {
+      "anyOf": [
+        {
+          "type": "number"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Page size used."
+    },
+    "nextOffset": {
+      "anyOf": [
+        {
+          "type": "number"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Offset of the next page; absent on the last page."
+    },
+    "offset": {
+      "anyOf": [
+        {
+          "type": "number"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Offset of this page."
+    },
+    "shownCount": {
+      "anyOf": [
+        {
+          "type": "number"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Number of items in this response."
+    },
+    "studies": {
+      "anyOf": [
+        {
+          "items": {},
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Studies: id, name, question count, dates, sharing state, Audiences with Mind counts, and links."
+    },
+    "totalCount": {
+      "anyOf": [
+        {
+          "type": "number"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Total number of items available."
+    }
+  },
+  "type": "object"
+}

Changed3 schema fields changedSep 18, 2026

addedInput schema / properties / limit

Added value: +{
+  "description": "Studies per page, newest first (default 20, max 100).",
+  "maximum": 100,
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / offset

Added value: +{
+  "description": "Number of Studies to skip; pass nextOffset from the previous page to continue.",
+  "maximum": 9007199254740991,
+  "minimum": 0,
+  "type": "integer"
+}

changedInput schema / properties / searchQuery / description

Previous value: -"Search for a Study by name (fuzzy matching supported)"New value: +"Search for a Study by name (fuzzy matching supported). Returns the best match."

AddedAug 27, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the agent knows this is a safe read operation. The description adds context about what the listing includes (audiences, mind counts, message counts, sharing state, links) and what it does not include (Minds and results, which come from study status). It also notes that deletion is not available. This adds value beyond annotations, but it does not describe the exact return structure or output schema, which is partially covered by the output 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?

The description is well-structured, with the main functionality in the first sentence and important exclusions and context in the second paragraph. It is not overly verbose, but the second paragraph could be slightly more concise. The key information is front-loaded, making it easy for an agent to quickly understand the tool's purpose.

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's moderate complexity, the description covers the essential aspects: what it lists, pagination, search behavior, and what it does not include. The output schema exists, so return values are documented. The description is sufficient for an agent to decide when to use this tool and what parameters to set, though it could be slightly more explicit about when to choose this over other list tools.

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?

The input schema documentation covers all three parameters with detailed descriptions, including limits, defaults, and how to continue pagination. The description adds context about pagination (nextOffset) and the behavior of searchQuery, but the schema already provides clear semantics. Since schema coverage is 100%, the description's added value is moderate but not critical.

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 verb 'Lists' with the resource 'the authenticated user's Studies' and specifies the ordering (most recently updated first) and pagination. It also distinguishes this tool from siblings by noting that Minds and results come from 'Study status' rather than this listing, and that deletion is not available here.

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?

The description clearly states the context of use: to list the user's studies with pagination, and mentions that searchQuery returns the best fuzzy name match instead of a page. However, it does not explicitly state when to use this tool versus alternatives like 'list_study_drafts' or 'list_study_templates', though the description implies the distinction by mentioning the full Study workspace and the lack of deletion.

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.