Skip to main content
Glama
Sign In
Placed MCP Server

Placed MCP Server

by Exidian-Tech
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

optimize_resume_for_job

Tailor your resume to a specific job description. Highlight keyword matches in optimized sections to pass applicant tracking systems.

Instructions

AI-powered resume optimizer that tailors your resume to match a specific job description. Returns optimized resume sections with keyword matches highlighted.

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_id": "<resume_id>",
      "job_description": "<job_description>"
    },
    "name": "optimize_resume_for_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
resume_idYesResume ID to optimize
job_descriptionYesTarget job description

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. It mentions AI-powered optimization and output format, but does not disclose whether the original resume is modified, if changes are reversible, or any side effects.

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 concise sentences that efficiently convey purpose and output. No unnecessary words or repetition.

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?

Given no output schema, description adequately indicates output type (optimized sections with keyword highlights). Could mention whether changes are saved or returned as a new version, but still generally complete for a simple tool.

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 covers both parameters with descriptions (resume_id, job_description). The description adds 'AI-powered' context, but no further parameter-specific details beyond what schema already provides.

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 clearly states the tool's purpose: tailors a resume to match a job description, returning optimized sections with keyword highlights. This distinguishes it from siblings like 'optimize_resume_section' and 'generate_cover_letter'.

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

Usage Guidelines2/5

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

No explicit guidance on when to use this tool versus alternatives. Siblings like 'check_ats_compatibility', 'improve_bullet_point', or 'optimize_resume_section' exist but are not mentioned, leaving the agent to infer context.

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

Deploy Server

Other Tools