Skip to main content
Glama

save_profile

Stores your job seeker profile—including skills, target roles, location, and experience—so you can reuse it for job matching, resume tailoring, and application tracking.

Instructions

Save your job seeker profile (name, skills, target roles, location)

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": {
      "name": "<name>",
      "targetRoles": "<targetRoles>",
      "skills": "<skills>",
      "experienceYears": "<experienceYears>"
    },
    "name": "save_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
emailNo
skillsYesYour key skills
locationNo
remoteOnlyNo
targetRolesYesRoles you are targeting e.g. ['Software Engineer', 'Data Analyst']
experienceYearsYesTotal years of work experience

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden and does little with it. 'Save' implies a write, but nothing discloses whether existing profile data is replaced or merged, whether partial updates are allowed, or whether authentication is required. With zero annotation coverage this is a significant gap for a mutation tool.

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?

A single front-loaded sentence with no wasted wording. The parenthetical field list is slightly misleading because it reads as exhaustive while covering only four of seven parameters.

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

Completeness2/5

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

For a 7-parameter mutation tool with no annotations and no output schema, the description is thin. It says nothing about overwrite behavior, required fields, or the result of the call, so an agent could invoke it with an incomplete or destructive payload.

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 only 43%, so the description needs to compensate and only partially does: it names name, skills, target roles and location. It omits experienceYears, which is one of the four required parameters, plus email and remoteOnly, leaving an agent with no signal that experienceYears is mandatory.

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 ('Save') and resource ('your job seeker profile'), which is enough for an agent to distinguish it from get_profile and save_resume by polarity (write vs read) and object (profile vs resume). It stops short of an explicit sibling differentiation, so it lands at 4 rather than 5.

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?

There is no guidance on when to use this versus get_profile or save_resume, and no statement of prerequisites. Critically, it never says whether saving overwrites an existing profile or creates one, which is the main decision an agent faces here.

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