Skip to main content
Glama

create_job_application

Destructive

Creates a new job application entry in GigHQ, or reuses an existing active one for the same company+job if the backend finds one — check alreadyExist in the response. Calling find_job_application first is still recommended when you want to inspect a possible match before deciding.

New applications always start in PROSPECTING status — there is no way to create directly into APPLIED/INTERVIEWING/etc. If the user has already applied, call update_job_application_status with status "APPLIED" right after this returns.

Optionally pass source_url and/or job_description to save them in the same call — attached best-effort after the application is created/found. If that secondary save fails, the create/find itself still succeeds and a warning is included in the response instead of an error. When an existing application is reused, supplied posting details can replace its saved source URL or job description.

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": {
      "company": "<company>",
      "job": "<job>",
      "context": "<context>"
    },
    "name": "create_job_application"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobYesThe job title or role you applied for.
companyYesThe name of the company you applied to.
contextYesA few words on why you are calling this tool, for the server developer's analytics. Describe people and things by role, such as "a customer". Do not quote the user or include names, emails, or other personal details.
llm_modelNoThe model identifier you are running as, for example "claude-opus-4-8" or "gpt-5.2". Pass "unknown" if you are not certain. Recorded for the server developer's analytics.
source_urlNoThe URL of the job posting, if known. Saved best-effort after create/find.
conversation_idNoThe conversation_id this server returned earlier in this conversation, unchanged, including after later user messages. Omit it if you have none. Recorded for the server developer's analytics.
job_descriptionNoThe full job description text, if known. Saved best-effort after create/find.

Output Schema

NameRequiredDescriptionDefault
uuidNo
appUrlNo
warningsNo
applicationYes
alreadyExistNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / context
      Added value: +{
      +  "description": "A few words on why you are calling this tool, for the server developer's analytics. Describe people and things by role, such as \"a customer\". Do not quote the user or include names, emails, or other personal details.",
      +  "type": "string"
      +}
    • addedInput schema / properties / conversation_id
      Added value: +{
      +  "description": "The conversation_id this server returned earlier in this conversation, unchanged, including after later user messages. Omit it if you have none. Recorded for the server developer's analytics.",
      +  "type": "string"
      +}
    • addedInput schema / properties / llm_model
      Added value: +{
      +  "description": "The model identifier you are running as, for example \"claude-opus-4-8\" or \"gpt-5.2\". Pass \"unknown\" if you are not certain. Recorded for the server developer's analytics.",
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "company",
      -  "job"
      -]New value: +[
      +  "company",
      +  "job",
      +  "context"
      +]
  2. Changed2 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedOutput schema / required
      Added value: +[
      +  "application"
      +]
  3. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only give the readOnly/destructive/openWorld triad; the description supplies the meaningful behaviors: new applications always land in PROSPECTING, the backend may silently reuse an existing record (check `alreadyExist`), and source_url/job_description are saved best-effort so a secondary failure yields a warning rather than an error. It also explains the destructiveHint=true annotation by noting that supplied posting details can replace an existing saved URL or description on reuse.

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?

Front-loaded with the core create-or-reuse behavior, then status semantics, then optional fields, then the reuse-overwrite caveat — a sensible information hierarchy. Slightly verbose in the find_job_application hedge ("still recommended when you want to inspect") and it partially restates the schema's "best-effort" note.

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?

An output schema exists so return values need not be documented, yet the description still flags the one field an agent must actually branch on (`alreadyExist`). Together with the status invariant, partial-failure behavior, and recommended follow-up call, nothing needed to invoke this correctly is missing.

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 baseline is 3; the description earns an extra point by adding semantics the schema does not carry — that source_url/job_description are attached after create/find on a best-effort basis with partial-failure semantics, and that on reuse they overwrite existing values. context, conversation_id, and llm_model are left entirely to the schema, which is acceptable given its coverage.

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+resource (creates a job application entry in GigHQ) and immediately adds the non-obvious dedup scope: it may reuse an existing active entry for the same company+job. That distinguishes it from find_job_application, which is named as the inspection-only alternative.

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?

Explicit sequencing guidance: use find_job_application first when you want to inspect a possible match, and call update_job_application_status with "APPLIED" right after creation if the user has already applied. It also states a hard exclusion — there is no way to create directly into APPLIED/INTERVIEWING — which prevents a whole class of wrong calls.

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.