Skip to main content
Glama

AceRound AI Interview Copilot

update_job_application_progress

Set the hiring progress of a submitted application. Values: NO_RESPONSE no reply / SCREENING_PASSED resume passed screening / WRITTEN_TEST assessment / INTERVIEW interview invited or in progress / OFFER offer / REJECTED rejected. (Requires the user's sign-in with scope job_applications:write.)

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>",
      "progress": "<progress>"
    },
    "name": "update_job_application_progress"
  }
}

Input Schema

NameRequiredDescriptionDefault
progressYes
applicationIdYesApplication id, from list_job_applications or the reply of an add-to-list tool

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds real context beyond that: the required sign-in and the job_applications:write scope, which an agent needs before invoking. It does not disclose idempotency, whether invalid transitions are rejected, or reversibility of a progress change.

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?

The core action is front-loaded in one sentence, followed by the value glossary and the auth note. Every element earns its place, though the slash-delimited enum list is dense to read and could be formatted more scannably.

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 two-parameter mutation tool with no output schema, the definition covers the action, all enum values, and the auth scope. Remaining gaps are transition rules (e.g., whether REJECTED can be followed by OFFER) and the response shape, which are secondary but relevant for a state-changing call.

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 only 50%, and the undocumented parameter is the enum, which the description compensates for fully by glossing all six values (NO_RESPONSE, SCREENING_PASSED, WRITTEN_TEST, INTERVIEW, OFFER, REJECTED). applicationId is already described in the schema, so the description adds no extra meaning there.

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 and resource: 'Set the hiring progress of a submitted application.' An agent can tell this is the progress-mutation tool. It does not, however, distinguish itself from close siblings such as mark_job_application_failed, which plausibly overlaps with the REJECTED value.

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?

The precondition 'of a submitted application' implicitly scopes usage, but there is no explicit when-to-use/when-not-to-use guidance and no named alternative (e.g., mark_job_application_failed vs progress=REJECTED). The agent must infer the boundary from sibling names alone.

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