Skip to main content
Glama

TrueInterview

Sync my résumé from my file

import_resume

Replace the candidate's saved résumé with the whole of a résumé file they keep on their computer (Markdown, text, a PDF or a Word file): read the file yourself and pass its text. TrueInterview's résumé reader turns it into the structured résumé the site uses, it is saved, and the answer has it back with a link to it as a PDF in their saved style, ready to upload. When the candidate edits their résumé file, sync it with this without asking again: they made the change, so it is their own words (the host still asks for its own approval). Pass only a file the candidate pointed you to. For one or two sections, update_resume is lighter. The résumé as it was is filed in their library on the site first, and nothing is saved when that fails. Reading the file uses the candidate's monthly writing allowance; writing_allowance says what is left. With no job search saved yet, suggested_search is what the résumé points at (roles, seniority, places), not saved: confirm it with the candidate in one line and save their answer with update_job_search.

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": {
      "text": "<text>"
    },
    "name": "import_resume"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesThe résumé's text, as read from the file.
filenameNoThe file's name, e.g. "resume.md": it names the library copy of the résumé this replaces.
include_resume_fileNoRender the saved résumé as a PDF and return a link to it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations (non-read-only, non-idempotent, non-destructive), it discloses that the old résumé is filed in the library first and nothing saves if that step fails, that reading consumes the candidate's monthly writing allowance, and that suggested_search is returned unsaved. It also notes the host's own approval step, which matters for a tool the agent is told to call without asking again.

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?

Purpose is front-loaded in the first sentence and every clause carries real information, but the long multi-clause sentences pile allowance, library copy and suggested_search into a dense block that is harder to scan than it needs to be.

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?

With no output schema, the description fully covers the return value (the structured résumé plus a PDF link in the saved style), the failure behavior, the cost/quota implication, and the unsaved suggested_search follow-up. An agent has everything needed to call it and handle the result correctly.

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%, so all three parameters are already documented, and the description largely restates the input contract. It does add one useful clarification — the agent must read the file itself and pass the text, not a path — but filename and include_resume_file are only echoed, not extended, so the baseline applies.

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 — replace the candidate's saved résumé with the whole of a file — and names the accepted formats and the parse-and-save pipeline. It also distinguishes itself from update_resume for one or two sections, so an agent can separate the two without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit triggers (sync when the candidate edits their file, without re-asking), the opposite case routed to update_resume, a hard constraint (pass only a file the candidate pointed you to), and a prescribed follow-up path via suggested_search and update_job_search. Nothing about when to use it is left to inference.

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