Skip to main content
Glama

Resumeily

Get 'Open & Save on Resumeily' link

get_import_link
Read-onlyIdempotent

Returns the link where the user saves the resume draft to their Resumeily account (sign-up or login), edits it and downloads the PDF.

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": {
      "draft_token": "<draft_token>"
    },
    "name": "get_import_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
draft_tokenYesPrivate token that identifies the resume draft (returned when the draft is created).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful context beyond that: the link drives a sign-up/login and PDF download flow rather than returning resume data. It still omits link lifetime, whether it is single-use, and whether repeated calls yield the same URL.

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?

A single front-loaded sentence that identifies the return value first and then its purpose. No filler, though the phrase 'edits it and downloads the PDF' is slightly run-on relative to the tool's actual job.

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?

With one required parameter, full schema coverage, read-only annotations, and no output schema, the description is the only place return-value meaning lives — and it does explain what the returned link enables. Remaining gaps (expiry, one-time use, URL format) are minor for a simple link-retrieval tool.

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%, and draft_token is fully documented as the private token returned at draft creation. The description adds nothing about the parameter, which is acceptable given the schema carries it, so the baseline 3 applies.

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 states a specific verb and resource ('Returns the link') and explains what that link is for: saving a draft to the user's Resumeily account, editing, and downloading the PDF. It does not name or contrast with any sibling such as create_resume or preview_resume, so differentiation must be inferred from the name alone.

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 only implied — the required draft_token and the 'save on Resumeily' framing suggest this is called after a draft exists, as a handoff step. There is no explicit when-to-use, when-not-to-use, or named alternative among the siblings.

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