Skip to main content
Glama

Resumeily

Preview resume

preview_resume
Read-onlyIdempotent

Returns an image of the first page of the resume draft (rendered exactly like the final PDF) plus the preview and 'Open & Save on Resumeily' links.

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

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

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint false, closed-world), so the description's job is to add context, which it does by disclosing the return payload: a rendered first-page image plus preview and 'Open & Save' links. It also usefully states the rendering is identical to the final PDF, which matters for judging preview fidelity. It does not say anything about failure behavior for bad tokens, keeping it short of a 5.

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?

A single well-formed sentence with the primary output (the first-page image) front-loaded and the secondary outputs (links) trailing. Every clause carries information; nothing is redundant with the title or annotations.

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 one-parameter, read-only preview tool with no output schema, the description is nearly sufficient: it explains what comes back and how faithful the rendering is. It stops short of covering multi-page behavior (whether other pages can be previewed) or token failure handling, which are minor gaps given the tool's simplicity.

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?

There is a single parameter with 100% schema description coverage, so the schema already explains draft_token as the private draft identifier. The description adds no further parameter detail (no format, no example, no note on where to obtain the token beyond what the schema says). Baseline 3 applies.

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 names a specific verb ('Returns an image') and a precise resource and scope ('first page of the resume draft'), plus the rendering guarantee ('exactly like the final PDF'). No sibling tool (create_resume, update_resume, get_import_link, list_templates) overlaps with this read-only rendering behavior, so an agent can distinguish it immediately.

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: an agent can infer this is for visually checking a draft before export or delivery, and the required draft_token suggests it must follow draft creation. There is no explicit statement of when to call this versus when not to, and no mention of error cases such as an invalid or expired token.

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