Skip to main content
Glama

Update a tracked job application

updateApplication
DestructiveIdempotent

Move a tracked application to another stage (draft, applied, assessment, ghosted, interview, offer, rejected) or edit its notes, title, company, link or job description. Only the fields given change; pass null to clear notes, jobUrl or jobDescription.

The job tracker also shows every Clera intro except withdrawn ones, but these tools only cover the jobs the candidate tracks themselves; listMyPipeline covers intros. Moving a card never contacts the company.

Clera privately records this tool's inputs and results for usage tracking and support.

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": {
      "applicationId": "<applicationId>"
    },
    "name": "updateApplication"
  }
}

Input Schema

NameRequiredDescriptionDefault
notesNo
stageNo
jobUrlNo
positionNo
companyNameNo
applicationIdYesThe id from a listApplications or trackApplication result.
jobDescriptionNo

Output Schema

NameRequiredDescriptionDefault
applicationYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the annotations it adds genuine behavioral detail: patch semantics ('Only the fields given change'), explicit null-clearing rules for notes, jobUrl and jobDescription, an assurance that stage moves are internal and never contact the company, and a data-recording disclosure. This is consistent with destructiveHint=true and idempotentHint=true and meaningfully reduces the risk of an agent mis-editing or clearing fields unintentionally.

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 short paragraphs, front-loaded with the core action and field list before scope and side-effect caveats. Each block carries information, though the privacy/recording sentence is boilerplate and slightly dilutes an otherwise tight definition.

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

Completeness4/5

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

For a destructive, idempotent mutation with an output schema present, the description covers what changes, what does not change, how to clear fields, scope versus intros, and side effects — so an agent can call it safely. The only meaningful gap is the field-name mapping between prose and schema and any permission or constraint context.

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?

With only 14% schema description coverage the description has to compensate; it names the editable fields and the null-clearing behavior, and lists the stage enum values, which is real added meaning. But it uses looser labels ('title', 'company', 'link') than the actual parameter names (position, companyName, jobUrl), leaving the agent to infer the mapping, and it says nothing about the length or format constraints that live in the schema.

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?

The description opens with a specific verb and resource ('Move a tracked application to another stage') and enumerates both the stage values and the editable fields ('notes, title, company, link or job description'). It also explicitly carves out scope against a sibling by stating listMyPipeline covers intros, so an agent can separate the two 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 Guidelines4/5

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

It gives clear usage context — these tools only cover jobs the candidate tracks themselves, with listMyPipeline as the stated alternative for intros — and clarifies that moving a card never contacts the company. It does not, however, address when to prefer this over siblings like updateProspects, updateRoleSearch, or deleteApplication, so there is no full when/when-not routing.

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