Skip to main content
Glama

Add my resume from a link

importResumeFromLink

Save a new resume from a public share link, the same as uploading it on the dashboard: Google Drive or iCloud Drive, PDF, DOC or DOCX, up to 10 MB, shared as "Anyone with the link". It becomes the candidate's primary resume, the one Clera sends with introductions, and parsing starts straight away; listResumes shows it.

A file that only sits on the candidate's computer can't travel through chat: send them getTalentDashboardLink upload_resume, which opens the upload box on their resume page.

Clera privately records this tool's inputs and results for usage tracking and support.

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": {
      "url": "<url>"
    },
    "name": "importResumeFromLink"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe share link to the resume file, exactly as the candidate gave it.

Output Schema

NameRequiredDescriptionDefault
fileNameYes
resumesLinkYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations, it discloses the side effects that matter: the resume becomes the candidate's primary one used by Clera for introductions, and parsing starts immediately. It also states hard constraints (Drive/iCloud share link, PDF/DOC/DOCX, 10 MB, 'Anyone with the link') and a privacy note about input/result recording, none of which the annotations convey.

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 action and its dashboard equivalent, then the constraints, then the alternative path — a sensible ordering. The closing privacy/usage-tracking sentence is boilerplate that doesn't help the agent call the tool, though it is short and clearly separated.

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 one-parameter write tool with annotations and an output schema present, the description covers formats, size limit, sharing requirement, primary-resume side effect, immediate parsing, and the alternate path for local files. Nothing an agent needs to decide or call correctly is missing.

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% for the single url parameter, so the baseline is 3; the description earns a point by enumerating what kinds of links are valid (Google Drive, iCloud Drive) and emphasizing the link must be exactly as the candidate provided it. It does not add URL syntax or validation nuance beyond that.

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 first sentence gives a specific verb and resource ("Save a new resume from a public share link") and immediately anchors it to a familiar equivalent ("the same as uploading it on the dashboard"). It also separates this tool from the sibling path for local files, so an agent can distinguish it without opening a 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?

The second paragraph states the explicit when-NOT case: a file that only lives on the candidate's computer cannot travel through chat, so the agent should send getTalentDashboardLink upload_resume instead. It also names listResumes as the place the saved resume appears, giving both the alternative and the follow-up verification path.

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