Skip to main content
Glama

extract_job_apply_profile_from_resume

Read-only

Draft Auto Apply profile values from one of the user's resumes (the most recently updated one if resumeId is omitted), and list fields missing from both resume and profile. Returns suggestions only; save them with update_job_apply_profile after the user confirms. (Requires the user's sign-in with scope job_applications:read.)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "extract_job_apply_profile_from_resume"
  }
}

Input Schema

NameRequiredDescriptionDefault
resumeIdNoResume id, from list_resumes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description reinforces this by stating 'Returns suggestions only', removing any doubt that data is persisted. It adds non-schema behavioral context in the form of an auth scope requirement (job_applications:read) and the confirmation gate before saving, though it says nothing about limits on how many fields are drafted or error 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?

Two compact sentences plus a bracketed auth note, front-loaded with the core action and the suggestion-only constraint. Every clause carries information: action, default, return contents, follow-up tool, and prerequisite scope.

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 one-parameter, non-destructive read with no output schema, the description covers the action, default behavior, what is returned, and the required permission. An agent has everything needed to call it correctly and to know it must then confirm with the user.

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 coverage is 100%, so the single parameter is already documented, but the description adds meaning beyond it by specifying the fallback to the most recently updated resume when resumeId is omitted. That optionality/default behavior is exactly the kind of semantics a schema cannot express.

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 ('Draft Auto Apply profile values from one of the user's resumes') plus a secondary output ('list fields missing from both resume and profile'). It names the sibling that persists the result, so an agent can distinguish drafting from saving 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?

Explicitly frames this as a suggestion-only step and directs the agent to update_job_apply_profile 'after the user confirms', giving both the alternative and the condition that selects it. It also states the default behavior when resumeId is omitted, so the call is unambiguous.

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