Skip to main content
Glama

Regenerate Cover Letter

regenerate_cover_letter

Regenerate an existing cover letter with optional feedback. Creates a revision linked to the source cover letter. Deducts credits (regeneration discount may apply). You may pass jobListingId from list_user_job_listings (omit companyName/role/jobPosition) instead of sending full job fields. Prefer get_user_profile (and optionally get_cover_letter_cost with sourceCoverLetterId) first so you know the user can afford regeneration. After success, tell the user to open the returned viewUrl on the website for a proper formatted view and easy access to templates.

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": {
      "sourceCoverLetterId": "<sourceCoverLetterId>"
    },
    "name": "regenerate_cover_letter"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleNoJob role / title. Required when jobListingId is not provided.
toneNoCustom tone content (required when toneTemplate is "custom")
filesNoPreviously uploaded files (CV/resume) from list_user_files. Prefer these when present. Optional when personBio holds user-confirmed background from chat.
feedbackNoRequested changes to apply to the regenerated cover letter
languageNoISO language code, e.g. "en"en
jobMarketNoJob market index: 0=Europe, 1=NorthAmerica, 2=SouthAndCentralAmerica, 3=MiddleEastAndAfrica, 4=AsiaPacific
keyPointsNoUp to 7 key points to highlight (max 50 chars each)
personBioNoCandidate bio / background. When list_user_files returns no CV/resume, use a bio the user confirmed in chat (they may have edited your draft). Draft from grounded data when available; never invent experience, skills, or education. Prefer uploaded files when available; personBio alone is enough to create without files.
personNameNoCandidate full name
companyNameNoTarget company name. Required when jobListingId is not provided.
jobPositionNoFull job description. Required when jobListingId is not provided.
jobListingIdNoID from list_user_job_listings. When provided, company/role/job description are loaded from the saved listing — omit companyName, role, and jobPosition.
toneTemplateNoTone template key, e.g. energetic, professional, customenergetic
desiredLengthNoLength scale 0-4 (0=very short, 4=highly elaborate)
personProfessionNoCandidate profession / title
sourceCoverLetterIdYesID of the cover letter to regenerate

Output Schema

NameRequiredDescriptionDefault
idYes
kindYes
roleNo
titleNo
statusYes
excerptNo
viewUrlYes
keyWordsNo
languageNo
createdAtNo
authorNameNo
companyNameNo
countryCodeNo
creditsUsedNo
languageLabelNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / files / maxItems
      Added value: +4
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations declare readOnlyHint=false and idempotentHint=false, and the description corroborates that a new revision is created rather than the source mutated, then adds non-obvious consequences the annotations cannot express: credits are deducted and a 'regeneration discount may apply'. It also closes the loop with a post-success instruction about the returned viewUrl, which is exactly the operational context an agent needs.

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?

Front-loaded with purpose and side effects before the input strategy and the post-success step, and every sentence carries distinct information (revision linkage, credits, ID shortcut, prerequisite check, viewUrl). The final sentence is a touch dense with comma-joined clauses, which keeps it from a 5.

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

Completeness5/5

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

For a 16-parameter, credit-consuming mutation with an output schema, the description covers the side effects, the recommended prerequisite calls, the alternative input path, and what to tell the user afterwards. Return-value formatting is not repeated, correctly deferring to the output schema except for the actionable viewUrl guidance.

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

Parameters4/5

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

Schema description coverage is 100%, so the baseline is 3; the description earns one extra point by consolidating the conditional input strategy in prose ('jobListingId ... omit companyName/role/jobPosition') and naming the sibling tool that produces that ID. Most field-level meanings, however, are already spelled out in the schema itself, so it does not add a full tier of new semantics.

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?

States a specific verb and resource ('Regenerate an existing cover letter') and immediately disambiguates the outcome: 'Creates a revision linked to the source cover letter.' The qualifier 'existing' implicitly separates it from create_cover_letter in the sibling set, so an agent can pick it without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit preconditions ('Prefer get_user_profile (and optionally get_cover_letter_cost with sourceCoverLetterId) first so you know the user can afford regeneration') and an alternative input path ('pass jobListingId from list_user_job_listings ... instead of sending full job fields'). The only implicit part is when to prefer create_cover_letter, which the word 'existing' in the first sentence already signals.

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