JobMojito

List interviews and positions

list_interviews

Read-onlyIdempotent

[Interviews] List the merchant's interviews and positions, with lifecycle, category, tags, recruiter and step count; filter by lifecycle, recruiter_profile_id or interview_category. type=interview (the default) also lists multi-stage positions.

Every argument in full, with examples: get_tool_reference.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_interviews"
  }
}

Input Schema

Name	Required	Description	Default
`type`	No	Which kind to list. Values: `interview` (default): interviews, assessments, interview role-plays \| `coaching`: coaching sessions and coaching personas \| `assessment`: assessments only \| `persona`: coaching personas only \| `persona_interview`: interview role-plays only \| `public_avatar`: public avatars.	interview
`limit`	No	Maximum number of records to return (1–1000).
`offset`	No	Number of records to skip from the start of the result set.
`status`	No	Filter by publication status (preparing: a draft still being prepared; completed: finished, read as closed). Omit to include all statuses.
`lifecycle`	No	Only multi-stage positions in this vacancy lifecycle (as lifecycle_status shows it). Interviews have no lifecycle, so this lists positions only.
`llm_model`	No	Your model id, e.g. "claude-opus-4-8"; "unknown" if unsure. For analytics.
`show_demo`	No	Include demo/sample interviews.
`filter_text`	No	Case-insensitive search on the interview name.
`merchant_id`	No	Optional merchant to scope to. Admins and sub-merchant operators only; other callers always use their token's merchant.
`show_public`	No	Include interviews shared publicly across merchants (coaching/avatars).
`filter_emoji`	No	Filter by the interview emoji marker.
`conversation_id`	No	The conversation_id this server returned earlier in this conversation, unchanged, including after later user messages. Omit it if you have none. Recorded for the server developer's analytics.
`interview_category`	No	Only definitions in this job category (case and surrounding spaces ignored).
`recruiter_profile_id`	No	Only definitions owned by this recruiter (`profile_id` (list_users)).

Output Schema

Name	Required	Description
`data`	Yes
`pagination`	Yes
`_mcp_instructions`	No	Server-issued metadata for this conversation.

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedNov 9, 2026

changedInput schema / properties / recruiter_profile_id / description

Previous value: -"Only definitions owned by this recruiter (profile.id)."New value: +"Only definitions owned by this recruiter (`profile_id` (list_users))."

changedInput schema / properties / show_demo / default
```
Previous value: -"false"New value: +false
```
removedInput schema / properties / show_demo / enum
```
Removed value: -[
-  "true",
-  "false"
-]
```
changedInput schema / properties / show_demo / type
```
Previous value: -"string"New value: +"boolean"
```
changedInput schema / properties / show_public / default
```
Previous value: -"false"New value: +false
```
removedInput schema / properties / show_public / enum
```
Removed value: -[
-  "true",
-  "false"
-]
```
changedInput schema / properties / show_public / type
```
Previous value: -"string"New value: +"boolean"
```

changedInput schema / properties / status / description

Previous value: -"Filter by publication status (type_interview_status). Omit to include all statuses."New value: +"Filter by publication status (preparing: a draft still being prepared; completed: finished, read as closed). Omit to include all statuses."

changedInput schema / properties / type / description

Previous value: -"Product type of interviews to list."New value: +"Which kind to list. Values: `interview` (default): interviews, assessments, interview role-plays | `coaching`: coaching sessions and coaching personas | `assessment`: assessments only | `persona`: coaching personas only | `persona_interview`: interview role-plays only | `public_avatar`: public avatars."

Changed46 schema fields changedNov 9, 2026
- removedInput schema / properties / lifecycle / example
```
Removed value: -"open"
```
- removedInput schema / properties / limit / example
```
Removed value: -50
```
- addedInput schema / properties / llm_model
```
Added value: +{
+  "description": "Your model id, e.g. \"claude-opus-4-8\"; \"unknown\" if unsure. For analytics.",
+  "type": "string"
+}
```
- removedInput schema / properties / merchant_id / example
```
Removed value: -"28106cba-1c27-4e53-b149-32113e5e8e31"
```
- removedInput schema / properties / offset / example
```
Removed value: -0
```
- removedInput schema / properties / show_demo / example
```
Removed value: -"false"
```
- removedInput schema / properties / show_public / example
```
Removed value: -"false"
```
- removedInput schema / properties / status / example
```
Removed value: -"active"
```
- removedInput schema / properties / type / example
```
Removed value: -"interview"
```
- removedOutput schema / properties / data / description
```
Removed value: -"The merchant's interview definitions for this page, newest-updated first."
```
- removedOutput schema / properties / data / items / properties / billing_single_position / description
```
Removed value: -"Single-position billing flag."
```
- removedOutput schema / properties / data / items / properties / billing_single_position_end_at / description
```
Removed value: -"Single-position billing end (ISO 8601)."
```
- removedOutput schema / properties / data / items / properties / calc_duration / description
```
Removed value: -"Calculated duration."
```
- removedOutput schema / properties / data / items / properties / cover_image_url / description
```
Removed value: -"Cover image URL."
```
- removedOutput schema / properties / data / items / properties / created_at / description
```
Removed value: -"Creation timestamp (ISO 8601)."
```
- removedOutput schema / properties / data / items / properties / emoji / description
```
Removed value: -"Emoji marker."
```
- removedOutput schema / properties / data / items / properties / environment / description
```
Removed value: -"Environment (production/test/…)."
```
- removedOutput schema / properties / data / items / properties / id / description
```
Removed value: -"Interview definition id."
```
- removedOutput schema / properties / data / items / properties / interview_category / description
```
Removed value: -"Job category (free text)."
```
- removedOutput schema / properties / data / items / properties / interview_count / description
```
Removed value: -"Number of interviews run against this definition."
```
- removedOutput schema / properties / data / items / properties / interview_last / description
```
Removed value: -"Timestamp of the most recent interview (ISO 8601)."
```
- removedOutput schema / properties / data / items / properties / is_ats / description
```
Removed value: -"Whether the interview is ATS-integrated."
```
- removedOutput schema / properties / data / items / properties / is_multi_stage / description
```
Removed value: -"Whether the interview is multi-stage."
```
- removedOutput schema / properties / data / items / properties / lifecycle_status / description
```
Removed value: -"Multi-stage positions: the vacancy lifecycle (stored, else derived from the publication status: draft/preparing = draft, active = open, archived/completed = closed). Absent for interviews."
```
- removedOutput schema / properties / data / items / properties / merchant_id / description
```
Removed value: -"Owning merchant id."
```
- removedOutput schema / properties / data / items / properties / mojito_language_code / description
```
Removed value: -"Platform language code."
```
- removedOutput schema / properties / data / items / properties / name / description
```
Removed value: -"Interview name."
```
- removedOutput schema / properties / data / items / properties / recording / description
```
Removed value: -"Per-answer recording/proctoring mode."
```
- removedOutput schema / properties / data / items / properties / recording_full_session / description
```
Removed value: -"Full-session recording mode."
```
- removedOutput schema / properties / data / items / properties / recruiter_profile_id / description
```
Removed value: -"Owning recruiter (profile.id)."
```
- removedOutput schema / properties / data / items / properties / speech_language_code / description
```
Removed value: -"Speech language code."
```
- removedOutput schema / properties / data / items / properties / status / description
```
Removed value: -"Publication status (type_interview_status)."
```
- removedOutput schema / properties / data / items / properties / step_count / description
```
Removed value: -"Multi-stage positions: live steps you can read (0 for a hiring manager account, which cannot read steps). Absent for interviews."
```
- removedOutput schema / properties / data / items / properties / tags / description
```
Removed value: -"Free-form tags."
```
- removedOutput schema / properties / data / items / properties / type / description
```
Removed value: -"Product type (interview/coaching/…)."
```
- removedOutput schema / properties / data / items / properties / type_avatar / description
```
Removed value: -"Avatar type used by the interview."
```
- removedOutput schema / properties / data / items / properties / updated_at / description
```
Removed value: -"Last update timestamp (ISO 8601)."
```
- removedOutput schema / properties / data / items / properties / visibility / description
```
Removed value: -"Visibility (merchant_public/invite/unlisted/…)."
```
- removedOutput schema / properties / pagination / properties / has_more / description
```
Removed value: -"True when more records exist beyond this page (offset + returned < total)."
```
- removedOutput schema / properties / pagination / properties / has_more / example
```
Removed value: -true
```
- removedOutput schema / properties / pagination / properties / limit / description
```
Removed value: -"Page size used for this response."
```
- removedOutput schema / properties / pagination / properties / limit / example
```
Removed value: -50
```
- removedOutput schema / properties / pagination / properties / offset / description
```
Removed value: -"Offset used for this response."
```
- removedOutput schema / properties / pagination / properties / offset / example
```
Removed value: -0
```
- removedOutput schema / properties / pagination / properties / total / description
```
Removed value: -"Total matching records across all pages."
```
- removedOutput schema / properties / pagination / properties / total / example
```
Removed value: -137
```

Changed10 schema fields changedNov 8, 2026

addedInput schema / properties / interview_category

Added value: +{
+  "description": "Only definitions in this job category (case and surrounding spaces ignored).",
+  "type": "string"
+}

addedInput schema / properties / lifecycle

Added value: +{
+  "description": "Only multi-stage positions in this vacancy lifecycle (as lifecycle_status shows it). Interviews have no lifecycle, so this lists positions only.",
+  "enum": [
+    "draft",
+    "pending_approval",
+    "open",
+    "applications_closed",
+    "on_hold",
+    "filled",
+    "cancelled",
+    "closed"
+  ],
+  "example": "open",
+  "type": "string"
+}

addedInput schema / properties / recruiter_profile_id

Added value: +{
+  "description": "Only definitions owned by this recruiter (profile.id).",
+  "format": "uuid",
+  "type": "string"
+}

changedInput schema / properties / status / description

Previous value: -"Filter by lifecycle status. Omit to include all statuses."New value: +"Filter by publication status (type_interview_status). Omit to include all statuses."

addedOutput schema / properties / data / items / properties / interview_category

Added value: +{
+  "description": "Job category (free text).",
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / data / items / properties / lifecycle_status

Added value: +{
+  "description": "Multi-stage positions: the vacancy lifecycle (stored, else derived from the publication status: draft/preparing = draft, active = open, archived/completed = closed). Absent for interviews.",
+  "enum": [
+    "draft",
+    "pending_approval",
+    "open",
+    "applications_closed",
+    "on_hold",
+    "filled",
+    "cancelled",
+    "closed",
+    null
+  ],
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / data / items / properties / recruiter_profile_id

Added value: +{
+  "description": "Owning recruiter (profile.id).",
+  "type": [
+    "string",
+    "null"
+  ]
+}

changedOutput schema / properties / data / items / properties / status / description

Previous value: -"Lifecycle status."New value: +"Publication status (type_interview_status)."

addedOutput schema / properties / data / items / properties / step_count

Added value: +{
+  "description": "Multi-stage positions: live steps you can read (0 for a hiring manager account, which cannot read steps). Absent for interviews.",
+  "type": [
+    "number",
+    "null"
+  ]
+}

addedOutput schema / properties / data / items / properties / tags

Added value: +{
+  "description": "Free-form tags.",
+  "items": {
+    "type": "string"
+  },
+  "type": [
+    "array",
+    "null"
+  ]
+}

Changed1 schema field changedNov 6, 2026

changedInput schema / properties / conversation_id / description

Previous value: -"Pass the exact conversation_id from the server's previous response, unchanged. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it. Keep passing the same conversation_id for the rest of the conversation, including after later user messages or on a different task; do not reset it when the user starts a new request."New value: +"The conversation_id this server returned earlier in this conversation, unchanged, including after later user messages. Omit it if you have none. Recorded for the server developer's analytics."

Changed1 schema field changedSep 27, 2026

changedInput schema / properties / conversation_id / description

Previous value: -"Echo the conversation_id from the server's previous response. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it."New value: +"Pass the exact conversation_id from the server's previous response, unchanged. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it. Keep passing the same conversation_id for the rest of the conversation, including after later user messages or on a different task; do not reset it when the user starts a new request."

Changed2 schema fields changedSep 23, 2026

addedInput schema / properties / conversation_id

Added value: +{
+  "description": "Echo the conversation_id from the server's previous response. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it.",
+  "type": "string"
+}

addedOutput schema / properties / _mcp_instructions

Added value: +{
+  "description": "Server-issued metadata for this conversation.",
+  "properties": {
+    "conversation_id": {
+      "description": "The server-issued conversation identifier.",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedJul 30, 2026

TDQS

A3.6/5.0

Behavior3/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds a useful behavioral detail in noting that the lifecycle filter restricts results to positions because interviews have no lifecycle. Beyond that it does not disclose pagination behavior, result volume, or aggregation semantics across the six type values, which is a meaningful gap for a 14-parameter list tool.

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 sentences, front-loaded with what is returned and then what can be filtered, with zero filler. The trailing pointer to get_tool_reference is slightly boilerplate but earns its place by offloading the exhaustive argument documentation.

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?

With an output schema, rich annotations, and a full-coverage input schema, the description does not need to explain return values or argument formats. It covers scope and the one non-obvious behavioral rule (lifecycle applies to positions only) and redirects to a reference tool for the rest. A brief note on default result size or cross-type aggregation would make it complete.

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 the schema already documents every parameter including enum meanings and defaults. The description only restates three filter names that the schema defines more fully and adds no format, interaction, or precedence guidance (for example how status interacts with lifecycle). Baseline 3 is appropriate.

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?

"List the merchant's interviews and positions" names a specific verb and resource, and the enumeration of returned fields (lifecycle, category, tags, recruiter, step count) plus the filterable fields makes the tool's scope concrete. It does not name a sibling tool it must be distinguished from, so it falls just short of a 5.

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?

It states the conditions under which the tool is appropriate (filter by lifecycle, recruiter_profile_id or interview_category) and clarifies that type=interview, the default, also returns multi-stage positions. There are no explicit exclusions or named alternatives, but the pointer to get_tool_reference gives the agent a clear next step for the remaining semantics.

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

All JobMojito 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.