Skip to main content
Glama

AceRound AI Interview Copilot

mark_job_application_failed

Mark an application as not submitted this time, with the reason (signed out, site error, blocked, etc.). Replies with the status as read back. (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>",
      "reason": "<reason>"
    },
    "name": "mark_job_application_failed"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonYesWhy it was not submitted
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 and destructiveHint=false, and the description adds genuinely new context: the required auth scope job_applications:write and the fact that the status is read back after the write, giving the agent verification behavior. The "this time" phrasing also implicitly signals the state is retryable rather than terminal, though it doesn't spell out what happens to downstream progress state.

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 sentences, front-loaded with the action and its qualifying reason, with the auth note correctly relegated to a trailing parenthetical. Nothing is redundant, though the parenthetical could be trimmed without loss.

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 with no output schema, the description covers the action, the reason space, the auth requirement, and the return behavior ("status as read back"). The only gap is the absence of any statement about how this differs from the sibling submitted/abandon tools.

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 the baseline is 3; the description earns above that by supplying concrete example reason values (signed out, site error, blocked) that go beyond the schema's generic "Why it was not submitted". It does not, however, clarify the applicationId sourcing beyond what the schema description already states.

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?

Description gives a specific verb and resource ("mark an application as not submitted") and scopes it with "this time", which makes it distinguishable from a permanent abandonment. It does not name its obvious counterpart mark_job_application_submitted or clarify the difference from abandon_job_application, so it falls just short of full sibling differentiation.

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 reason examples (signed out, site error, blocked) imply the triggering situations, so the when-to-use case is inferable. However, there is no explicit exclusion or routing statement telling the agent to call mark_job_application_submitted instead when submission succeeded, or abandon_job_application when the application should be dropped entirely.

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