Skip to main content
Glama

get_cover_letter_prompt

Generates a personalized cover letter-writing prompt from a job description, company name, and optional tone to help draft a targeted application letter.

Instructions

Generate a prompt to write a personalized cover letter for a job

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>",
      "companyName": "<companyName>"
    },
    "name": "get_cover_letter_prompt"
  }
}

Input Schema

NameRequiredDescriptionDefault
toneNoprofessional
companyNameYes
jobDescriptionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full behavioral burden. It clarifies the important prompt-versus-letter distinction, but does not describe the generated prompt's contents, whether profile or resume information is incorporated, or any other operational behavior.

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?

The single sentence is front-loaded, easy to parse, and contains no filler. It compactly communicates both the action and the important distinction that the tool generates a writing prompt.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple three-parameter generator, the description provides enough core purpose for basic selection, while the schema supplies required flags and tone choices. Nevertheless, with no output schema and no parameter descriptions, it should add that the company name and job description drive personalization and that tone controls style, along with clearer differentiation from sibling career tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, yet the description names none of jobDescription, companyName, or tone. "Personalized" and "for a job" weakly suggest job-related inputs, but the description does not explain the two required fields or how the optional tone affects the result; the schema's property names, enum, and default do most of the work.

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 clearly pairs the verb "Generate" with the resource "a prompt to write a personalized cover letter for a job," and usefully indicates that the output is a prompt rather than explicitly a finished letter. It does not explicitly differentiate itself from related siblings such as get_resume_tailoring_prompt, so it falls 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 wording implies use when someone wants a job-specific prompt to help draft a personalized cover letter. However, it provides no explicit when-to-use or when-not-to-use guidance and does not explain when this tool should be chosen over other resume, job-match, or application tools.

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