User Intuition

Get Interview

get_interview

Read-onlyIdempotent

Get interview timing, stored format, current configured study language, and up to 100 spoken transcript segments bounded to about 20 KB of text. Use next_message_offset to fetch the next page. Each segment keeps its original turn ID and text_offset; system prompts and internal metadata are excluded.

Input Schema

TableJSON Schema

Name	Required	Description
`interview_id`	Yes
`message_limit`	No
`message_offset`	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	The full requested interview.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 4, 2026

changedOutput schema / properties / result / 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"
+}

Changed22 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 / interview_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 / message_offset / maximum
```
Added value: +9007199254740991
```

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 / duration_seconds / anyOf

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

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

changedOutput schema / properties / result / properties / messages / anyOf

Previous value: -[
-  {
-    "items": {
-      "additionalProperties": false,
-      "properties": {
-        "end_s": {
-          "type": "number"
-        },
-        "id": {
-          "type": "string"
-        },
-        "message": {
-          "type": "string"
-        },
-        "role": {
-          "enum": [
-            "participant",
-            "moderator"
-          ],
-          "type": "string"
-        },
-        "start_s": {
-          "type": "number"
-        },
-        "text_offset": {
-          "type": "integer"
-        }
-      },
-      "required": [
-        "id",
-        "role",
-        "message"
-      ],
-      "type": "object"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "items": {
+      "additionalProperties": false,
+      "properties": {
+        "end_s": {
+          "type": "number"
+        },
+        "id": {
+          "type": "string"
+        },
+        "message": {
+          "type": "string"
+        },
+        "role": {
+          "enum": [
+            "participant",
+            "moderator"
+          ],
+          "type": "string"
+        },
+        "start_s": {
+          "type": "number"
+        },
+        "text_offset": {
+          "maximum": 9007199254740991,
+          "minimum": -9007199254740991,
+          "type": "integer"
+        }
+      },
+      "required": [
+        "id",
+        "role",
+        "message"
+      ],
+      "type": "object"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]

changedOutput schema / properties / result / properties / next_message_offset / anyOf

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

changedOutput schema / properties / result / properties / participant / anyOf

Previous value: -[
-  {
-    "additionalProperties": true,
-    "properties": {
-      "email": {
-        "$ref": "#/properties/result/properties/study_id"
-      },
-      "id": {
-        "$ref": "#/properties/result/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 / quality / $ref
```
Removed value: -"#/properties/result/properties/study_id"
```
addedOutput schema / properties / result / properties / quality / type
```
Added value: +[
+  "string",
+  "null"
+]
```

changedOutput schema / properties / result / properties / screener_responses / anyOf

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

removedOutput schema / properties / result / properties / status / $ref
```
Removed value: -"#/properties/result/properties/study_id"
```
addedOutput schema / properties / result / properties / status / type
```
Added value: +[
+  "string",
+  "null"
+]
```
addedOutput schema / properties / result / properties / total_message_segments / maximum
```
Added value: +9007199254740991
```
addedOutput schema / properties / result / properties / total_message_segments / minimum
```
Added value: +-9007199254740991
```

First observedSep 30, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description adds genuine behavioral context beyond that: a ~20 KB text bound, a 100-segment cap, and the guarantee that system prompts and internal metadata are excluded while turn IDs and text_offsets are preserved.

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 dense sentences that front-load the returned payload before pagination guidance. Efficient overall, though the incorrect parameter name in the second sentence costs a point.

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?

An output schema exists, so return-value shape need not be re-explained, and the description still covers the key operational facts an agent needs: content bounds, pagination, and what is filtered out. The only gap is the misnamed pagination parameter and no guidance on sibling selection.

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 only 25%, so the description is expected to compensate. It hints at the limit and pagination but references 'next_message_offset', which is not a real parameter (the schema uses message_offset) — a naming error that actively misleads. organization_id is documented only in the schema.

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?

States a specific verb (get) and resource (interview), then enumerates exactly what comes back: timing, stored format, study language, and spoken transcript segments. That enumeration clearly distinguishes it from siblings like list_interviews and get_interview_usage_stats.

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 gives real usage guidance for pagination ('Use next_message_offset to fetch the next page'), which is more than most definitions offer. However, it never states when to prefer this over list_interviews or get_interview_usage_stats, and the pagination pointer names a field that does not exist in the schema.

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?