GetMattered

Generate Interview Questions

getmattered_generate_interview_questions

Builds interview prep questions for a role and company, by application_id or by job title and company. Uses AI credits.

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

Input Schema

Name	Required	Description
`job_title`	No	Title of the position (e.g. "Senior Software Engineer"). Used with company_name, or replaced by application_id.
`company_name`	No	Name of the company. Used with job_title, or replaced by application_id.
`application_id`	No	The application whose job the prep is for (an id from getmattered_get_applications). Replaces job_title and company_name.
`job_description`	No	Full text of the job description (optional but recommended for better results)

Output Schema

Name	Required	Description
`jobId`	Yes
`prepUrl`	Yes
`jobTitle`	Yes
`setupStep`	No	Present while account setup is open: the first setup step.
`companyName`	Yes
`questionsToAsk`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 8, 2026

changedOutput schema / properties / setupStep / description

Previous value: -"Set while account setup is open: the step to take first."New value: +"Present while account setup is open: the first setup step."

Changed3 schema fields changedNov 8, 2026

changedInput schema / properties / application_id / description

Previous value: -"Prep for the job of this application (an id from getmattered_get_applications). Replaces job_title and company_name."New value: +"The application whose job the prep is for (an id from getmattered_get_applications). Replaces job_title and company_name."

changedInput schema / properties / company_name / description

Previous value: -"Name of the company. Pass with job_title, or pass application_id instead."New value: +"Name of the company. Used with job_title, or replaced by application_id."

changedInput schema / properties / job_title / description

Previous value: -"Title of the position (e.g. \"Senior Software Engineer\"). Pass with company_name, or pass application_id instead."New value: +"Title of the position (e.g. \"Senior Software Engineer\"). Used with company_name, or replaced by application_id."

Changed1 schema field changedNov 6, 2026

addedOutput schema / properties / setupStep

Added value: +{
+  "description": "Set while account setup is open: the step to take first.",
+  "type": "string"
+}

First observedOct 24, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already cover openWorldHint=true, non-idempotent and non-destructive behavior, so the bar is lower. The description adds genuinely non-obvious context: the call consumes AI credits, which matters for agent decision-making about repeated invocation.

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

Conciseness5/5

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

Two short sentences, front-loaded with the purpose and ending with the cost note. Nothing redundant or padded.

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 present, return values need not be explained, and annotations cover the safety profile. The definition covers both input modes and cost; the only gap is that all four parameters are technically optional, so it doesn't clarify whether some combination is effectively required.

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 100% and the schema itself already explains the application_id vs job_title/company_name relationship and the optional job_description. The description only restates the two input modes, adding no syntax or constraint detail beyond structured fields.

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 a specific verb (builds) and resource (interview prep questions), and scopes it to a role/company. An agent can distinguish it from siblings like generate_cover_letter or analyze_job_description by the output artifact, though no sibling is named explicitly.

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?

It gives input-mode guidance ('by application_id or by job title and company'), which implies when each parameter set applies, but offers no explicit when-to-use/when-not versus adjacent tools such as analyze_job_description or optimize_resume.

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

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