Skip to main content
Glama

Resumeily

Create resume

create_resume

Creates a temporary resume draft on Resumeily from structured resume content. Returns a preview of the first page, a private draft_token that identifies the draft, and an 'Open & Save on Resumeily' link where the resume can be saved to a Resumeily account.

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": {
      "resume": "<resume>"
    },
    "name": "create_resume"
  }
}

Input Schema

NameRequiredDescriptionDefault
fontNoOne of: Arial, Helvetica, Times New Roman, Georgia, Verdana, Courier New, Roboto, Open Sans, Lato, Montserrat, Poppins, Rubik, Inter, Playfair Display, Merriweather.
titleNoResume title, e.g. 'Jane Doe – Frontend Developer'.
colorsNo
resumeYesResume content. Every section is optional.
templateNoTemplate id, such as 'classic', 'modern' or 'slate'. Defaults to 'classic'.

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?

Annotations already declare this is a non-read-only, non-destructive, non-idempotent write, so the description's job is to add context beyond that — and it does: the draft is temporary, the call returns a first-page preview plus a private draft_token, and persistence only happens via the 'Open & Save on Resumeily' link. It stops short of stating draft expiry or authentication requirements, which matter for a tool that mints a private token.

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?

Two tightly written sentences that front-load the action and follow with the return contract. Every clause carries information — the temporariness, the three returned artifacts, and the save path — with no filler.

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 no output schema, the description correctly takes on the burden of explaining what comes back: a first-page preview, a private draft_token, and a save link. That covers the main ambiguity for a create-draft tool; only draft lifetime and whether the token must be reused in a subsequent update call are left unstated.

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 coverage is 80%, with detailed per-field descriptions for the nested resume object, font, colors and template, so the schema does the heavy lifting. The description adds only the word 'structured' and no guidance on the mutually exclusive bullets-vs-description pattern in experience, so it neither compensates for nor extends the schema meaningfully. 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?

States a specific verb and resource ('Creates a temporary resume draft on Resumeily from structured resume content') and adds the key qualifier that the draft is temporary, which distinguishes it from a persistent save. It does not explicitly contrast itself with sibling tools like preview_resume or update_resume, so an agent must infer the boundary.

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 agent can infer it should call this to start a new draft rather than preview or update an existing one. There is no explicit when-to-use guidance, no mention of when to prefer preview_resume instead, and no stated prerequisites or limits on how many drafts can exist.

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