Skip to main content
Glama

Read interviews

get_interviews
Read-onlyIdempotent

The member's interviews, rounds, briefings, people, playbooks, company research, calendar feed and question sets. Actions: list, follow_ups, get, briefing, people, playbook, company_intel, calendar_feed, question_set. Call with action "help" for each action's fields.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "action": "<action>"
    },
    "name": "get_interviews"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes
paramsNoFields for the action. Call with action "help" to list each action's fields.
event_idNoAn interview round's id (a process's interviews[].id) from get_interviews list.
interview_idNoAn interview's id from get_interviews list, or a follow_ups item's processId.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / event_id / description
      Previous value: -"An interview round's id from get_interviews get."New value: +"An interview round's id (a process's interviews[].id) from get_interviews list."
  2. Changed1 schema field changed
    • changedInput schema / properties / interview_id / description
      Previous value: -"An interview's id from get_interviews list."New value: +"An interview's id from get_interviews list, or a follow_ups item's processId."
  3. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered structurally. The description adds essentially nothing beyond that profile — no pagination, result shape, or volume limits — except the notable workflow hint that per-action fields require a "help" round-trip.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The help pointer is front-loaded usefully, but the first sentence is a redundant noun list that largely duplicates the action enumeration in the second sentence. Two enumerations of the same underlying surface cost space without adding discrimination.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a 10-action, nested-params dispatch tool with no output schema and no descriptions on the action enum; for that complexity the description should route between actions and describe return shapes. Instead it offloads all of that to a separate help invocation, leaving the agent unable to call correctly without a preliminary call.

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 75%, with event_id and interview_id documented in-schema (including the distinctive note that follow_ups items expose processId). But 'action' has 10 enum values with zero in-schema explanation, and 'params' is a free-form object; the description only restates the action names and defers field meaning entirely to a help call rather than compensating for the gap.

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 names the resources returned (interviews, rounds, briefings, people, playbooks, company research, calendar feed, question sets) and enumerates the read actions, so an agent knows this is the read-side accessor for interview data. It never explicitly contrasts with the write-side sibling manage_interviews, so the purpose is clear but the boundary is inferred from naming convention alone.

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?

Action names ('list', 'follow_ups', 'get', 'briefing') imply their own usage well enough for an agent to pick plausibly, and the pointer to action "help" gives a discovery path. However there is no explicit guidance on choosing between actions, no prerequisite or scope conditions, and no statement that writes belong to manage_interviews.

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.