Skip to main content
Glama

Check a background task

get_task_status
Read-only

Report a background task by the task_id a tool returned (create_profile, translate_resume, request_resume_update, export_resume_pdf, start_radar_scan, apply_vacancy_resume_suggestions, generate_cover_letter and the analyze_* tools): status processing | completed | failed | cancelled, progress, on failure the reason, and on success what it produced — the new resume's resume_id, the translated copy's resume_id, the resume_id a rewrite changed (get_resume reads it) and the sections it kept as they were (guarded_sections), whether the PDF is ready, how many postings a scan found, the app_url of a written cover letter. Returns 'not_found' if the task does not exist or does not belong to the current user.

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": {
      "input": "<input>"
    },
    "name": "get_task_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYes

Output Schema

NameRequiredDescriptionDefault
typeYesWhat the task does, e.g. 'resume_translation', 'resume_update', 'pdf_generation', 'radar_scan', 'apply_suggestions', 'vacancy_analysis', 'resume_suggestions', 'cover_letter_generation', 'offer_analysis'.
errorNoSet when status is 'failed'.
resultNoSet when status is 'completed'.
statusYes'processing' covers a task waiting in the queue and one running.
task_idYes
progressNo0–100 while it runs, when the task reports it.
created_atYesWhen the task was started, ISO 8601.
completed_atNoWhen it finished or failed, ISO 8601.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / $defs / TaskResult / properties / nothing_changed
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "boolean"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "For a rewrite: true when it finished without changing anything in the resume; update_message says why. Absent when it changed something.",
      +  "title": "Nothing Changed"
      +}
    • addedOutput schema / $defs / TaskResult / properties / update_message
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Why a rewrite that changed nothing left the resume as it was.",
      +  "title": "Update Message"
      +}
  2. Changed1 schema field changed
    • addedOutput schema / $defs / TaskResult / properties / guarded_sections
      Added value: +{
      +  "anyOf": [
      +    {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "For a rewrite: sections (by section name, e.g. 'summary', 'experience') the rewrite came back with empty or with fewer entries although the request was not read as a removal, so their previous content was kept. update_resume_section clears or trims a section directly.",
      +  "title": "Guarded Sections"
      +}
  3. Changed1 schema field changed
    • addedOutput schema / $defs / TaskResult / properties / unchanged_count
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "integer"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Suggestions that changed nothing: the resume states nothing they build on.",
      +  "title": "Unchanged Count"
      +}
  4. Changed3 schema fields changed
    • addedOutput schema / $defs / TaskResult / properties / best_company
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Company of that strongest new posting.",
      +  "title": "Best Company"
      +}
    • addedOutput schema / $defs / TaskResult / properties / best_match_id
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "The strongest of the postings this scan found new: its radar match id.",
      +  "title": "Best Match Id"
      +}
    • addedOutput schema / $defs / TaskResult / properties / best_title
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Job title of that strongest new posting.",
      +  "title": "Best Title"
      +}
  5. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already mark this as a safe read-only operation, and the description adds substantial behavior beyond that: possible statuses, progress reporting, failure reasons, success payloads by task type, guarded_sections, PDF readiness, scan counts, cover-letter app_url, and the not_found case for missing or unauthorized tasks.

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 description is front-loaded with the core action and the task_id source, then enumerates status values and result types. It is dense and long, but nearly every clause adds useful information for interpreting varied task outputs.

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?

For a one-parameter polling tool with annotations and an output schema, the description covers the lifecycle, statuses, failure reporting, task-type-specific success outputs, and ownership-related not_found behavior. Nothing essential for correct invocation 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 description coverage is reported as 0%, so the description must carry the parameter meaning. It explains that task_id comes from a tool that runs in the background and lists the producer tools, which compensates well, though it does not state the expected format of the ID.

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 states a specific verb and resource: 'Report a background task by the task_id'. It also names the async tools that produce task IDs, making its role distinct from direct tools like get_resume or get_radar_status.

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 clearly indicates when to use the tool: after create_profile, translate_resume, request_resume_update, export_resume_pdf, start_radar_scan, apply_vacancy_resume_suggestions, generate_cover_letter, or analyze_* tools return a task_id. It also points to get_resume for reading a rewritten resume, but does not explicitly exclude alternatives or mention competing status tools.

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.