Skip to main content
Glama

Prepare a full interview plan

prepare_interview_plan
Read-onlyIdempotent

Builds the full interview plan for a project, program or product manager (or a business analyst) from the resume text and, optionally, a job posting and a company name: every resume line a hiring manager is likely to press on, every company question with its source pages, and the questions arranged by interview stage (recruiter screen, hiring manager, panel, company round), with the grounding of the posting: every resume line word for word with its number, each requirement with a call (covered, partial, not_found, not_checked) and every resume line found for it, and checks, which says what each field means. The requirement questions follow those calls. Same inputs as prepare_interview_questions, including interview_stage, interviewer_title, interviewer_profile and draft; every question prepare_interview_questions gives for the same inputs, except its opening questions, is in the plan under the same id. Fixed rules, no model. Contact details are removed before the check; the resume and the posting sent with a call are not stored. Requires sign-in with a PM Career Desk account that has an Interview Coach Pass. handoff_code reads the resume and the job posting saved on the PM Career Desk site or in its Chrome extension; that code holds them for up to 2 hours.

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": "prepare_interview_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleNoOptional. One of project-manager, program-manager, technical-program-manager, product-manager, scrum-master, pmo, it-manager, business-analyst, delivery-manager; a title as written (for example Senior Program Manager) is also read. Empty when not sure.
draftNoOptional. A prep draft written from a result of this tool for the same resume and posting, up to 20000 characters. The result is then the check of the draft: its quotes that are not in the resume word for word, its gap calls on requirements where the rules found resume lines, its covered calls where they found none, and its figures not in the resume or the posting. The draft is read in memory only and not stored.
entryNoOptional. Where the person started: directory, site, udemy or other. Counted only; with handoff_code the code's own entry is used.
companyNoOptional. The employer's name as written in the posting.
industryNoOptional. The employer's industry, one of healthcare-life-sciences, financial-services, software-saas, government-public-sector, consulting-services, retail-supply-chain, manufacturing-industrial, energy-utilities; a plain name such as healthcare or banking is also read. Adds questions written for that industry. Empty when not sure.
job_postingNoThe full text of the job posting, as the person gave it. Optional; with it the result adds the requirements, the gaps and questions about them.
resume_textNoThe resume as plain text, copied in full from what the person pasted or from the text of the file they attached. At least the summary and the experience section. May be empty when handoff_code is given.
handoff_codeNoOptional. A handoff code PCD-XXXX-XXXX-XXXX-XXXX that the person made on the PM Career Desk site or in its Chrome extension. The resume and the job posting saved under it are read instead of resume_text and job_posting. A code works for 2 hours, and for 30 minutes after its first read.
interview_dateNoOptional. The interview date as YYYY-MM-DD.
resume_outlineNoOptional structure of the resume: roles with title, company, dates and bullets; summary; skills; certifications; education. Every line must appear word for word in resume_text; lines that do not are left out and counted in the result. Without it the plain text is read.
interview_stageNoOptional. The interview stage: recruiter_screen, hiring_manager, panel, company_round or unknown. Shifts the mix of intro, requirement, resume line and behavioral questions.
job_requirementsNoOptional. The requirement lines of the job posting, each word for word from job_posting; lines that are not are left out and counted in the result. Without them the requirements are read from job_posting.
interviewer_titleNoOptional. The interviewer's job title as the person gave it, up to 120 characters, for example Director of Engineering. Read for the function and level only; no name is needed.
interviewer_profileNoOptional. The text of the interviewer's profile that the person pasted, up to 3000 characters. Contact details are removed and only subject words of a fixed list are kept to choose questions; the text is not returned and not stored.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changed
    • addedInput schema / properties / draft
      Added value: +{
      +  "anyOf": [
      +    {
      +      "maxLength": 20000,
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": "",
      +  "description": "Optional. A prep draft written from a result of this tool for the same resume and posting, up to 20000 characters. The result is then the check of the draft: its quotes that are not in the resume word for word, its gap calls on requirements where the rules found resume lines, its covered calls where they found none, and its figures not in the resume or the posting. The draft is read in memory only and not stored.",
      +  "title": "Draft"
      +}
    • addedInput schema / properties / entry
      Added value: +{
      +  "anyOf": [
      +    {
      +      "enum": [
      +        "directory",
      +        "site",
      +        "udemy",
      +        "other"
      +      ],
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Optional. Where the person started: directory, site, udemy or other. Counted only; with handoff_code the code's own entry is used.",
      +  "title": "Entry"
      +}
    • addedInput schema / properties / handoff_code
      Added value: +{
      +  "anyOf": [
      +    {
      +      "maxLength": 64,
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": "",
      +  "description": "Optional. A handoff code PCD-XXXX-XXXX-XXXX-XXXX that the person made on the PM Career Desk site or in its Chrome extension. The resume and the job posting saved under it are read instead of resume_text and job_posting. A code works for 2 hours, and for 30 minutes after its first read.",
      +  "title": "Handoff Code"
      +}
    • addedInput schema / properties / interview_date
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": "",
      +  "description": "Optional. The interview date as YYYY-MM-DD.",
      +  "title": "Interview Date"
      +}
    • addedInput schema / properties / interview_stage
      Added value: +{
      +  "anyOf": [
      +    {
      +      "enum": [
      +        "recruiter_screen",
      +        "hiring_manager",
      +        "panel",
      +        "company_round",
      +        "unknown"
      +      ],
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Optional. The interview stage: recruiter_screen, hiring_manager, panel, company_round or unknown. Shifts the mix of intro, requirement, resume line and behavioral questions.",
      +  "title": "Interview Stage"
      +}
    • addedInput schema / properties / interviewer_profile
      Added value: +{
      +  "anyOf": [
      +    {
      +      "maxLength": 3000,
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": "",
      +  "description": "Optional. The text of the interviewer's profile that the person pasted, up to 3000 characters. Contact details are removed and only subject words of a fixed list are kept to choose questions; the text is not returned and not stored.",
      +  "title": "Interviewer Profile"
      +}
    • addedInput schema / properties / interviewer_title
      Added value: +{
      +  "anyOf": [
      +    {
      +      "maxLength": 120,
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": "",
      +  "description": "Optional. The interviewer's job title as the person gave it, up to 120 characters, for example Director of Engineering. Read for the function and level only; no name is needed.",
      +  "title": "Interviewer Title"
      +}
    • addedInput schema / properties / resume_text / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • addedInput schema / properties / resume_text / default
      Added value: +""
    • changedInput schema / properties / resume_text / description
      Previous value: -"The resume as plain text, copied in full from what the person pasted or from the text of the file they attached. At least the summary and the experience section."New value: +"The resume as plain text, copied in full from what the person pasted or from the text of the file they attached. At least the summary and the experience section. May be empty when handoff_code is given."
    • removedInput schema / properties / resume_text / type
      Removed value: -"string"
    • removedInput schema / required
      Removed value: -[
      -  "resume_text"
      -]
  2. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Goes well past the annotations: it discloses that the engine is 'Fixed rules, no model', that sign-in with an Interview Coach Pass is required, that contact details are stripped before the check, that the resume and posting are not stored, and that handoff codes expire after 2 hours. These are exactly the auth, determinism and data-retention facts the readOnly/idempotent hints cannot convey.

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 opening is front-loaded with purpose, but the core is a single sprawling colon-chained sentence ('...and checks, which says what each field means') that is hard to parse on first read. Content is largely substantive, but the packaging costs the reader effort it shouldn't.

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?

For a 14-parameter tool with no output schema, the description does real work: it sketches the return structure (word-for-word resume lines with numbers, requirement calls, source pages, per-field checks), states the sibling parity guarantee, and covers auth and storage. It stops short of edge cases such as supplying neither resume_text nor handoff_code, or what happens when the pass is missing.

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 baseline is 3 and the description adds little per-parameter meaning beyond naming interview_stage, interviewer_title, interviewer_profile and draft as shared with the sibling. Most of its prose describes the output shape rather than clarifying what individual inputs do.

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 and artifact ('Builds the full interview plan') and enumerates its contents: resume lines a hiring manager will press on, company questions with source pages, questions by interview stage, plus requirement calls. It also distinguishes itself from the sibling by declaring that every question prepare_interview_questions returns (except opening questions) appears in the plan under the same id.

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?

The superset relationship to prepare_interview_questions is made explicit, and the draft parameter's effect ('the result is then the check of the draft') tells the agent when to pass a draft rather than start fresh. There is no direct 'use this instead of X when...' sentence, so routing is inferred from the containment statement rather than stated outright.

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