Skip to main content
Glama

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

NameRequiredDescriptionDefault
interview_idYes
message_limitNo
message_offsetNo
organization_idNoOrganization for this operation and billing. Use list_organizations to choose an active membership.

Output Schema

NameRequiredDescriptionDefault
resultYesThe full requested interview.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / organization_id / description
      Previous value: -"Platform admins only: select an organization for this operation. Required when changing another organization’s study or using its wallet."New value: +"Organization for this operation and billing. Use list_organizations to choose an active membership."
  2. Changed1 schema field changed
    • 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"
      +]
  3. Changed1 schema field changed
    • 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"
      +}
  4. Changed22 schema fields changed
    • 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
  5. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior, and the description adds substantive traits beyond them: a 100-segment hard cap, an approximate 20 KB text bound, exclusion of system prompts/internal metadata, and preservation of turn ID and text_offset per segment.

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?

Three dense sentences that front-load the payload contents before the paging instruction; nearly every clause carries information, with the only waste being the mismatched next_message_offset label.

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 values need not be spelled out, and the description covers payload scope, size bounds, pagination, and content exclusions. Minor gaps remain around the offset field naming and error behavior for a bad interview_id.

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 coverage is only 25% (just organization_id), so the description must compensate; it partially does by implying the 100-segment ceiling and offset-based paging, but it never explains message_limit vs message_offset explicitly and references a name (next_message_offset) that does not match the schema (message_offset).

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 uses a specific verb+resource and enumerates exactly what a single interview record returns: timing, stored format, configured study language, and transcript segments. It is clearly distinct from list_interviews and get_interview_usage_stats, though it never explicitly says so.

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?

"Use next_message_offset to fetch the next page" is a genuine pagination hint, but the schema parameter is named message_offset, and no guidance is given for when to prefer this over list_interviews or how to combine message_limit with the ~20 KB cap.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources