Skip to main content
Glama

Save job to tracker

save_job
DestructiveIdempotent

Save a job to your application tracker. Uses the connected Himalayas account; no extra sign-in needed.

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": {
      "title": "<title>",
      "company_name": "<company_name>"
    },
    "name": "save_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
notesNoPersonal notes about this job
titleYesJob title
statusNoApplication status (default: saved)
app_linkNoApplication link URL
currencyNoSalary currency (e.g., 'USD')
excitementNoExcitement level from 0-5
max_salaryNoMaximum salary
base_salaryNoBase salary
company_nameYesCompany name
himalayas_linkNoHimalayas job listing URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly=false, idempotent=true, destructive=true and closed-world, so the safety profile is largely covered. The description adds the useful auth detail that it uses the connected Himalayas account with no extra sign-in, but says nothing about what happens if the same job is saved twice or whether existing fields are overwritten — meaningful gaps for a 10-parameter write tool, even though the known annotation set (idempotentHint) hints at duplicate handling.

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 short sentences with the core action front-loaded and the auth caveat second. Every sentence carries information and nothing is padded.

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 fully-documented schema with a safety profile supplied by annotations and no output schema to explain, the description covers what an agent needs: the action, the target (personal application tracker), and the credential context. Remaining questions (duplicate handling, return shape) are minor given idempotentHint and the absence of an output contract.

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 description coverage is 100% across all 10 parameters, including the status enum and required fields, so the schema does the heavy lifting. The description adds no parameter-level meaning beyond what the schema already documents, which is the expected baseline when coverage is complete.

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 states a specific verb+resource ('Save a job to your application tracker'), which is clearly distinct from read/delete siblings like get_saved_jobs and remove_saved_job. It does not, however, explicitly differentiate itself from adjacent write tools such as update_job_status or create_company_job, so an agent must infer that this is the create-an-entry path.

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 when-to-use guidance, no mention of alternatives (e.g., update_job_status for an existing tracked job), and no prerequisites beyond the auth note. An agent gets no help deciding between saving, updating, or removing a job entry.

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