Skip to main content
Glama

JobMojito

by com.jobmojito

Get interview result details

get_interview_result_details
Read-onlyIdempotent

[Results] Get full interview result details including transcript and scores. Scores are assistive output for a human reviewer.

Returns an interview result with its full transcript and AI assessment. Optionally attaches signed recording URLs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
interview_result_idYesThe interview result to fetch the transcript and details for.
get_signed_recordingsNoWhen true, includes short-lived signed recording URLs for the session, the video introduction, and each transcript answer.false

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
endNoInterview end timestamp (training_end, ISO 8601).
scoreNoOverall interview score.
startNoInterview start timestamp (training_start, ISO 8601).
statusNoCoach/interview status (coach_status), e.g. started, completed.
durationNoTotal duration in deciseconds (duration_ds).
score_textNoHuman-readable score summary.
transcriptNoOrdered interactions (questions + answers) of the interview.
ai_analysisNoCandidate-facing AI analysis of the whole interview.
score_answerNoAggregate answer sub-score.
recording_urlNoSigned session-recording URL; present only when get_signed_recordings=true.
recruiter_risksNoDetected recruiter risk flags (jsonb).
score_sentimentNoSentiment sub-score.
score_simulationNoOverall simulated score.
recording_is_videoNoWhether the session recording is video.
score_pronunciationNoPronunciation sub-score.
ai_completion_reasonNoWhy the interview completed (ai_completed_reason).
recording_local_pathNoStorage path of the full session recording.
ai_analysis_recruiterNoRecruiter-facing AI analysis of the whole interview.
score_words_per_minuteNoSpeaking-pace (words per minute) sub-score.
video_introduction_urlNoSigned video-introduction URL; present only when get_signed_recordings=true.
user_feedback_recruiterNoRecruiter-entered feedback note.
video_introduction_local_pathNoStorage path of the candidate video introduction.
ai_analysis_recruiter_why_hireNoReasons to hire (list/text).
ai_interview_coverage_percentageNoPercentage of the intended interview the AI judged to be covered.
ai_analysis_recruiter_why_not_hireNoReasons not to hire (list/text).

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint, describing the safety profile. The description adds context: scores are 'assistive output for a human reviewer' and recording URLs are optional. This goes beyond annotations without contradiction.

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?

The description is concise with four sentences, front-loading the main purpose. The use of '[Results]' as a tag adds categorization. However, the structure is slightly fragmented; grouping optional details more tightly could improve readability.

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

Completeness5/5

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

Given the tool's simplicity, presence of an output schema, and comprehensive annotations, the description covers key aspects: transcript, scores, AI assessment, and optional recordings. No further details (e.g., prerequisites, permissions) are necessary for this read-only tool.

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?

Both parameters (interview_result_id, get_signed_recordings) have clear descriptions in the input schema (100% coverage). The tool description mentions 'Optionally attaches signed recording URLs' but does not add new meaning beyond the schema. Baseline of 3 is appropriate.

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?

The description clearly states 'Get full interview result details including transcript and scores' and mentions optionally attaching recording URLs. This distinguishes it from sibling tools like list_interview_results which returns a list without details. The verb 'get' and resource 'interview result details' are specific and unambiguous.

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 implies usage when full details are needed (e.g., 'Get full interview result details') but does not explicitly state when to use this over alternatives like list_interview_results. No exclusions or 'when not to use' guidance is provided.

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

All JobMojito toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0
Disambiguation4/5

Most tools target distinct resources and actions, with clear category prefixes like [Interviews], [Results], and [Admin]. A few pairs could be confused—create_interview vs. create_interview_from_questions and update_interview vs. set_interview_state—but the descriptions do enough to separate them.

Naming Consistency4/5

The overwhelming majority follow a consistent verb_noun pattern: create_*, get_*, list_*, update_*, generate_*. The main deviation is jobmojito_configuration, which is a noun phrase rather than an action verb, and a few longer names like request_another_interview_attempt break the clean pattern slightly.

Tool Count2/5

With 29 tools, this server is above the 25+ threshold and places a significant navigation burden on an agent. The tools are organized into coherent domains, but several admin/merchant and results tools could likely be consolidated.

Completeness3/5

The core interview lifecycle is well covered: create, read, update, list, state changes, result retrieval, and report generation. However, there are notable gaps such as no delete operations for interviews or catalogue directories, no candidate management beyond listing/registration, and no explicit result-decision tool.

Resources