Skip to main content
Glama

Read a resume into Matchaa

import_resume

Use this only in the step-by-step path, when create_tailored_resume is unavailable or failed: reads a resume (attached PDF or pasted text) with the website's reader, without adapting it. For a new request to tailor a resume to a job post, use create_tailored_resume instead. Pass the attached PDF as cvFile rather than transcribing it yourself. Returns the read profile for review and an operationId to pass to tailor_resume as sourceOperationId. Exact retries reuse the same reading. Do not use for a job post; use analyze_job_offer.

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

Input Schema

NameRequiredDescriptionDefault
cvFileNo
cvTextNo
languageNofr
guestTokenYes

Output Schema

NameRequiredDescriptionDefault
errorNo
resultNo
statusYes
recoveryNo
downloadUrlNo
operationIdYes
expiresInSecondsNo
retryAfterSecondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing idempotency ('exact retries reuse the same reading'), the returned artifacts (read profile plus an operationId fed to tailor_resume as sourceOperationId), and a usage constraint on the file input. It does not explain why readOnlyHint is false despite the 'read' framing, or what guestToken requirement/identity flow applies, which keeps it below a 5.

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 gating condition, then alternatives, then input handling, then return value. Dense and mostly waste-free, though it reads as one long run-on sequence rather than clearly separated guidance blocks.

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 tool that produces an operation artifact, the description covers the crucial chaining contract (operationId to tailor_resume), the no-adaptation semantics, and retry idempotency, while the output schema handles return shape. The main remaining gap is the required guestToken/identity context for a tool that does create an operation.

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 0%, so the description must carry parameter meaning; it usefully covers cvFile (pass the attached PDF rather than transcribing) and implies cvText via 'pasted text'. It says nothing about the required guestToken or the fr/en language default, leaving two of four parameters undocumented anywhere.

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 ('reads a resume ... with the website's reader, without adapting it') and explicitly contrasts itself with named siblings create_tailored_resume and analyze_job_offer, so an agent can distinguish it 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 an explicit gating condition ('only in the step-by-step path, when create_tailored_resume is unavailable or failed'), names the preferred alternative for the common case, and adds a negative rule ('Do not use for a job post; use analyze_job_offer'). Very little 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