User Intuition

List Interviews

list_interviews

Read-onlyIdempotent

List lightweight interview rows. Fetch an interview to get messages, recordings, and screener responses.

Input Schema

TableJSON Schema

Name	Required	Description
`page`	No
`status`	No
`quality`	No
`study_id`	No
`page_size`	No
`participant_id`	No
`organization_id`	No	Platform admins only: select an organization for this operation. Required when changing another organization’s study or using its wallet.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes	Paginated interview summaries.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 4, 2026

changedOutput schema / properties / result / properties / interviews / items / properties / participant_source / enum

Previous value: -[
-  "byop",
-  "panel",
-  "external_panel",
-  "link",
-  "unknown"
-]New value: +[
+  "byop",
+  "panel",
+  "external_panel",
+  "link",
+  "synthetic",
+  "unknown"
+]

Changed1 schema field changedOct 1, 2026

addedInput schema / properties / organization_id

Added value: +{
+  "description": "Platform admins only: select an organization for this operation. Required when changing another organization’s study or using its wallet.",
+  "maxLength": 128,
+  "minLength": 1,
+  "type": "string"
+}

Changed23 schema fields changedSep 30, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

removedInput schema / additionalProperties
```
Removed value: -false
```
addedInput schema / properties / page / maximum
```
Added value: +9007199254740991
```

addedInput schema / properties / participant_id / 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)$"

addedInput schema / properties / study_id / 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)$"

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

changedOutput schema / properties / result / additionalProperties
```
Previous value: -trueNew value: +{}
```
changedOutput schema / properties / result / properties / interviews / items / additionalProperties
```
Previous value: -trueNew value: +{}
```

changedOutput schema / properties / result / properties / interviews / items / properties / duration_seconds / anyOf

Previous value: -[
-  {
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "maximum": 9007199254740991,
+    "minimum": -9007199254740991,
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / result / properties / interviews / items / properties / ended_at / $ref
```
Removed value: -"#/properties/result/properties/interviews/items/properties/started_at"
```
addedOutput schema / properties / result / properties / interviews / items / properties / ended_at / description
```
Added value: +"ISO 8601 timestamp."
```
addedOutput schema / properties / result / properties / interviews / items / properties / ended_at / type
```
Added value: +[
+  "string",
+  "null"
+]
```
removedOutput schema / properties / result / properties / interviews / items / properties / language / $ref
```
Removed value: -"#/properties/result/properties/interviews/items/properties/study_id"
```
addedOutput schema / properties / result / properties / interviews / items / properties / language / type
```
Added value: +[
+  "string",
+  "null"
+]
```

changedOutput schema / properties / result / properties / interviews / items / properties / participant / anyOf

Previous value: -[
-  {
-    "additionalProperties": true,
-    "properties": {
-      "email": {
-        "$ref": "#/properties/result/properties/interviews/items/properties/study_id"
-      },
-      "id": {
-        "$ref": "#/properties/result/properties/interviews/items/properties/study_id"
-      }
-    },
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": {},
+    "properties": {
+      "email": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "id": {
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / result / properties / interviews / items / properties / quality / $ref
```
Removed value: -"#/properties/result/properties/interviews/items/properties/study_id"
```
addedOutput schema / properties / result / properties / interviews / items / properties / quality / type
```
Added value: +[
+  "string",
+  "null"
+]
```
removedOutput schema / properties / result / properties / interviews / items / properties / status / $ref
```
Removed value: -"#/properties/result/properties/interviews/items/properties/study_id"
```
addedOutput schema / properties / result / properties / interviews / items / properties / status / type
```
Added value: +[
+  "string",
+  "null"
+]
```

changedOutput schema / properties / result / properties / page / anyOf

Previous value: -[
-  {
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "maximum": 9007199254740991,
+    "minimum": -9007199254740991,
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]

changedOutput schema / properties / result / properties / page_size / anyOf

Previous value: -[
-  {
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "maximum": 9007199254740991,
+    "minimum": -9007199254740991,
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]

addedOutput schema / properties / result / properties / total_count / maximum
```
Added value: +9007199254740991
```
addedOutput schema / properties / result / properties / total_count / minimum
```
Added value: +-9007199254740991
```

First observedSep 30, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds a real behavioral detail — that rows are lightweight and omit messages/recordings/screener responses — but says nothing about pagination or the cost/scale of the operation.

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 short sentences with zero filler, and the payload-shape constraint is front-loaded before the routing hint. Every sentence earns its place.

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?

An output schema exists, so return-value explanation is not required, and the description correctly frames the lightweight nature of the rows. However, with seven mostly-undocumented parameters and a filter-heavy list tool, the definition is thin on how to narrow results.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 14% (6 of 7 params undocumented), so the description carries the burden of explaining filters and adds nothing. Status, quality, study_id, participant_id, page and page_size are never mentioned, leaving an agent to infer filter semantics entirely from the schema.

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?

States a specific verb ('List') and resource ('interviews') and qualifies the payload as 'lightweight interview rows', which immediately distinguishes it from get_interview. The sibling is referenced obliquely ('Fetch an interview') rather than by name, so the routing is clear but not explicit.

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?

Gives a clear alternative condition: use the fetch path when you need messages, recordings, and screener responses, otherwise list. It doesn't mention any of the available filters (status, quality, study_id, participant_id), but the when-to-use-vs-alternative guidance is directly stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All User Intuition 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.

Resources

Need Help?