Skip to main content
Glama

AIApply

Add a resume to AIApply

add_resume
Destructive

Use this when get_setup_status says next_step is add_resume. Pass exactly one of: resume, the file the user attached, if you can attach files to tool calls; or resume_text, the content of their CV as you can read it, or the work history, education and skills the user tells you. Never invent or embellish anything. Returns suggested, the values to show the user next. Only for a first setup: another file replaces the one added before it; text cannot replace a file. Needs an AIApply account: if the user has not signed in, calling it asks them to sign in or create one. It also needs a permission the user grants; if it was not granted, calling it asks the user to allow it.

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

Input Schema

NameRequiredDescriptionDefault
resumeNoThe resume file the user attached (PDF or DOCX, at most 5 MB). Omit when sending resume_text.
resume_textNoThe resume as text, at most 30,000 characters. Omit when sending resume.

Output Schema

NameRequiredDescriptionDefault
addedNoTrue when the resume was added.
reasonNoWhy nothing was added, when nothing was.
sourceNofile or text.
appliedNo
messageYes
suggestedNoValues read from the resume, for the user to confirm.
user_messageNoShow this to the user rather than message.
preferences_urlNo
finish_setup_urlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

The annotations already declare destructiveHint=true and readOnlyHint=false; the description earns credit by explaining exactly what is destroyed (a prior file is replaced, and text cannot replace a file) and by disclosing two auth gates — an AIApply account and a user-granted permission — with the fallback behavior of prompting to sign in or allow. It also warns against fabricating resume content. It stops short of stating rate limits or whether the replacement is reversible.

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?

The trigger is front-loaded, then the parameter rule, then constraints and prerequisites in a sensible order. It is dense and information-bearing throughout, though the run-on sentence structure around 'Pass exactly one of' makes it 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.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be explained, and the description still names 'suggested' as what comes back. Trigger, exclusivity, replacement rules and both auth prerequisites are covered; only secondary behavior such as failure modes beyond the auth prompts is left implicit.

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 100%, so the baseline would be 3, but the description adds real semantics the schema does not: the parameters are mutually exclusive ('exactly one of'), and it tells the agent how to choose between them based on its own capability to attach files versus read text. It also instructs that resume_text may be assembled from work history, education and skills the user states, which is guidance absent from the schema.

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?

The description opens with a specific verb+resource (add a resume to AIApply) and immediately ties invocation to a concrete precondition, 'get_setup_status says next_step is add_resume'. That lets an agent place it precisely against siblings like get_setup_status and apply_to_job 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?

It names the exact trigger condition, states the mutually exclusive choice ('Pass exactly one of'), and sets an explicit exclusion: 'Only for a first setup'. It also clarifies the asymmetry that another file replaces the earlier one but text cannot, which is the practical guidance an agent needs when deciding whether to call it again.

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