Skip to main content
Glama

AceRound AI Interview Copilot

upload_job_apply_attachment

Upload an Auto Apply attachment (resume file, student ID, transcript, ID photo) and save it to that field of the user's profile, replacing the old file. File content is passed as base64; PDF and JPG / PNG / WebP up to 8 MB. Replies with the profile field as read back. (Requires the user's sign-in with scope job_applications: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": {
      "field": "<field>",
      "fileName": "<fileName>",
      "fileBase64": "<fileBase64>"
    },
    "name": "upload_job_apply_attachment"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldYesresumeFile / studentIdFile / transcriptFile / photoFile
fileNameYesFile name with extension
fileBase64YesFile content, base64

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the annotations, the description discloses the important behavior that the existing file is replaced, the transport format (base64), and the accepted media types and 8 MB ceiling, plus the required auth scope. That is real added context on top of readOnlyHint=false / destructiveHint=false, though the overwrite-on-replace semantics sit in mild tension with destructiveHint=false and the failure behavior is unstated.

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?

It is a single dense, front-loaded passage: action first, then content constraints, then return value, then the auth requirement in parentheses. Slightly compressed by slash-lists and parentheticals, but no sentence is wasted.

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 three-parameter write tool with no output schema, the description covers what is written, what is overwritten, format limits, auth needs, and even the response ('the profile field as read back'). Remaining gaps are minor: no error/validation behavior and no explicit routing to related profile tools.

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 already 100% for the three parameters, so the baseline is 3; the description goes further by tying the 'field' enum to actual document types and by imposing format/size semantics on fileBase64 (PDF, JPG, PNG, WebP, 8 MB max) that the schema does not express.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource ('Upload an Auto Apply attachment') and enumerates the concrete field targets (resume file, student ID, transcript, ID photo), so the agent knows exactly what the tool writes. It stops short of distinguishing itself from closely named siblings such as upload_resume or update_job_apply_profile, which the agent must resolve on its own.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: the reader infers this is the tool for pushing a local file into one of the four profile attachment fields. The prerequisite (user sign-in with job_applications:write scope) is given, but there is no explicit when-to-use/when-not guidance and no pointer to the alternative profile-mutation or resume-upload tools.

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