Skip to main content
Glama

capture_job

Idempotent

Save a requested job with separate responsibilities, requirements, preferred requirements, skills, education, benefits, original salary and extraction metadata. Supply source posting_text for gap filling. The server validates, fills evidenced gaps and converts salary to EUR. Return existing matches without overwriting them.

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": {
      "url": "<url>",
      "company_name": "<company_name>",
      "role_position": "<role_position>",
      "retry_id": "<retry_id>",
      "user_requested_capture": "<user_requested_capture>"
    },
    "name": "capture_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
skillsNo
countryNo
ai_modelNoActual assistant model if known; omit rather than guessing.
benefitsNo
locationNo
retry_idYes
educationNo
job_sourceNoother
descriptionNo
flexibilityNounknown
company_nameYes
posting_textNoSource posting text for detecting and filling extraction gaps. Never include career context.
requirementsNo
ai_confidenceNo
role_positionYes
salary_periodNounknown
source_job_idNo
application_urlNo
employment_typeNo
salary_currencyNo
responsibilitiesNo
extraction_reasonNo
extraction_warningsNo
salary_max_originalNo
salary_min_originalNo
experience_max_yearsNo
experience_min_yearsNo
preferred_requirementsNo
user_requested_captureYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

With annotations already declaring readOnlyHint=false, idempotentHint=true and destructiveHint=false, the description still adds real behavioral detail beyond them: the server validates, fills evidenced gaps from posting_text, converts salary to EUR, and returns existing matches instead of overwriting. It does not explain what a validation failure or response payload looks like, which matters since there is no output schema.

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?

Three sentences, front-loaded with the save action and its scope, then the posting_text hint, then the validation/idempotency contract. Dense and mostly waste-free, though the opening field enumeration is long and could be tightened without losing meaning.

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

Completeness3/5

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

For a 30-parameter mutation with no output schema and near-zero schema coverage, the description covers the main flow (save, validate, gap-fill, EUR conversion, no-overwrite) but omits what happens on validation failure and gives no meaning to the required control parameters. It is adequate scaffolding but not complete for a tool of this complexity.

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 7% across 30 parameters, so the description must carry the semantic load and largely does not. It names many list fields but leaves the required parameters (url, company_name, role_position, retry_id, user_requested_capture) and key optionals (flexibility, employment_type, experience_min/max_years, ai_confidence, source_job_id) completely unexplained, including no explanation of retry_id's role or why user_requested_capture must be true.

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 opens with a specific verb+resource ("Save a requested job") and enumerates the structured field groups it persists (responsibilities, requirements, preferred requirements, skills, education, benefits, salary, extraction metadata). It is distinguishable from siblings like save_assessments or record_prepared_application by its focus on raw job capture, though it never names or contrasts those siblings explicitly.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: "Supply source posting_text for gap filling" tells the agent one thing to do, and "Return existing matches without overwriting them" signals repeat-call behavior. There is no explicit when-to-use / when-not-to-use guidance relative to the sibling save_* tools an agent could confuse this with.

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