Skip to main content
Glama

TrueInterview

Tailor my résumé to a job

tailor_resume

Tailor the candidate's résumé to one job with TrueInterview's résumé tailoring: bullets reworded toward what the posting asks, the posting's terms surfaced where their work shows them, nothing invented (every line stays traceable to their own résumé, and a deterministic check reports anything that slipped). Returns the tailored résumé, what changed, and a link to it as a PDF to upload. Their saved résumé is not changed. Give exactly one of job_id, application_id, or job_description with company and role (job pages are not fetched here: read the posting and pass its text). It uses the candidate's monthly writing allowance; writing_allowance says what is left. Show the candidate the changes before you use the file.

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

Input Schema

NameRequiredDescriptionDefault
roleNo
job_idNo
companyNo
keywordsNoTerms from the posting the candidate wants on the résumé.
intensityNokeywords: only surface the posting terms; rewrite (default): reword bullets toward the role.
application_idNo
job_descriptionNo
include_resume_fileNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses the safety model ('nothing invented (every line stays traceable to their own résumé, and a deterministic check reports anything that slipped)'), that the saved résumé is untouched despite a write-style annotation set, that it consumes a monthly writing allowance, and that it does not fetch postings. This is meaningful context an agent could not infer from readOnlyHint=false / destructiveHint=false alone.

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?

Front-loaded with the action and what it produces, and essentially every clause carries information (safety, return values, allowance cost, input constraint, workflow). The run-on sentence packing several of these together hurts scanability slightly but wastes no words.

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 no output schema and 25% parameter coverage, the description carries the load well: it names the return payload (tailored résumé, what changed, PDF link), the cost mechanism, and the non-destructive guarantee. Remaining gaps are minor, such as how the caller observes remaining allowance ('writing_allowance says what is left' is vague) and the role of include_resume_file.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 25%, so the description must compensate, and it does for the highest-risk part: the mutual-exclusivity constraint across job_id, application_id, and job_description (with company/role) is stated nowhere in the schema. keywords and intensity are already documented in the schema, but include_resume_file (default true) is left unexplained in both places, leaving one real gap.

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 resource ('Tailor the candidate's résumé to one job') and immediately scopes what tailoring means: 'bullets reworded toward what the posting asks'. It also implicitly separates itself from fetching tools by warning 'job pages are not fetched here: read the posting and pass its text', so an agent can tell it apart from match_resume_to_job or get_job without opening the schema.

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?

Provides a concrete exclusivity rule ('Give exactly one of job_id, application_id, or job_description with company and role') plus a workflow instruction ('Show the candidate the changes before you use the file'). It does not name explicit alternatives or when-not-to-use cases, which keeps it just short of a 5.

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