Skip to main content
Glama

AceRound AI Interview Copilot

upload_resume

Upload a resume file (PDF / JPG / PNG / WEBP). The server reads its text and saves it as a new resume for interviews and Auto Apply. The file content is passed as base64. Returns the new resume id; read it back with get_resume. (Requires the user's sign-in with scope resumes:write.)

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": {
      "fileName": "<fileName>",
      "fileBase64": "<fileBase64>"
    },
    "name": "upload_resume"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNoResume title; defaults to the file name
fileNameYesFile name, such as "resume.pdf"
fileBase64YesFile content as base64

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?

Annotations already declare readOnlyHint=false and destructiveHint=false, so the write-but-non-destructive profile is covered. The description adds real value beyond that: the server performs text extraction from the file, the result is persisted as a new resume, and the call requires the resumes:write auth scope. It does not mention size limits or failure modes for unreadable files.

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?

Four tight sentences, front-loaded with the action and accepted formats, followed by processing behavior, return value, and the auth prerequisite. No filler or redundancy.

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?

For a three-parameter upload tool with no output schema, the description covers input format, server-side processing, persistence, the returned resume id, the follow-up read tool, and the required auth scope. Nothing an agent needs to invoke it correctly 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 all three parameters are already documented, including the title defaulting to the file name and fileBase64 holding base64 content. The description restates the base64 encoding but adds no new semantics, so the baseline 3 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 (upload) and resource (resume file), enumerates accepted formats (PDF/JPG/PNG/WEBP), and describes the outcome (text extracted, saved as a new resume for interviews and Auto Apply). An agent can distinguish this from create_resume_from_text purely on the file-vs-text basis.

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?

Gives clear context: use for file-based resume ingestion, then read back with get_resume, and requires sign-in with the resumes:write scope. It does not explicitly state when to prefer a sibling such as create_resume_from_text, so the alternative routing is left implicit.

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