Skip to main content
Glama

get_resume_tailoring_prompt

Generates a ready-to-use prompt that tailors your saved resume to a specific job description, so you can align skills and experience with each role before applying.

Instructions

Get a ready-to-use prompt for tailoring your saved resume to a specific job description

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": {
      "jobDescription": "<jobDescription>"
    },
    "name": "get_resume_tailoring_prompt"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobDescriptionYesPaste the full job description here

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral load; it does clarify the key trait that the tool returns a prompt rather than performing tailoring or modifying the resume, and that it reads the saved resume rather than supplied text. It omits what happens when no resume is saved and says nothing about output length, format, or any limits on job description size.

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 front-loaded sentence with no filler; the resource and the input condition are stated immediately and nothing is redundant with the title or schema.

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 prompt generator with no output schema, the description covers what is returned (a prompt) and what it operates on (your saved resume plus a job description). The main gap is the unstated dependency on a previously saved resume and behavior when none exists.

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 100% and the single parameter is already documented as 'Paste the full job description here' with a required flag. The description only reinforces that it should target one specific job description, adding little beyond the schema, so the baseline of 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+resource ('Get a ready-to-use prompt') plus the scope ('tailoring your saved resume to a specific job description'), which is enough to separate it from get_cover_letter_prompt and get_interview_prep by resource. It does not explicitly name or contrast those siblings, so it stops short of a 5.

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?

The phrase 'your saved resume' implies the precondition that a resume already exists in the account, which is useful implied guidance. However, there is no explicit when-to-use, when-not-to-use, or routing to alternatives such as analyze_job_match or get_cover_letter_prompt.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.