Skip to main content
Glama

track_application

Retrieve the current status and details of a job application using its unique ID.

Instructions

Get the current status and details of a job application by its ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
application_idYesJob application ID to look up

Implementation Reference

  • Schema definition for the track_application tool. It defines an 'application_id' required string parameter and a description of returning status and history.
    {
      name: 'track_application',
      description: 'Get the current status and full history of a job application.',
      inputSchema: {
        type: 'object',
        properties: {
          application_id: {
            type: 'string',
            description: 'Application ID returned by apply_to_job or list_job_applications',
          },
        },
        required: ['application_id'],
      },
    },
  • index.js:154-236 (registration)
    The track_application tool is registered as part of the WEEK2_TOOLS array (lines 177-190), which is merged into the tool list via handleToolsList (line 263) and proxied to the backend via handleToolsCall (line 279).
    const WEEK2_TOOLS = [
      {
        name: 'apply_to_job',
        description: 'Submit a job application through Placed. Attaches the candidate\'s resume and optional cover letter, then tracks the application.',
        inputSchema: {
          type: 'object',
          properties: {
            candidate_id: {
              type: 'string',
              description: 'Candidate profile ID (use "me" for the authenticated user)',
            },
            job_id: {
              type: 'string',
              description: 'Job listing ID to apply to',
            },
            cover_letter: {
              type: 'string',
              description: 'Optional cover letter text. If omitted, a cover letter is auto-generated from the candidate profile.',
            },
          },
          required: ['candidate_id', 'job_id'],
        },
      },
      {
        name: 'track_application',
        description: 'Get the current status and full history of a job application.',
        inputSchema: {
          type: 'object',
          properties: {
            application_id: {
              type: 'string',
              description: 'Application ID returned by apply_to_job or list_job_applications',
            },
          },
          required: ['application_id'],
        },
      },
      {
        name: 'post_job',
        description: 'Post a new job listing to the Placed job board (for employers/recruiters).',
        inputSchema: {
          type: 'object',
          properties: {
            title: {
              type: 'string',
              description: 'Job title (e.g. "Senior Backend Engineer")',
            },
            description: {
              type: 'string',
              description: 'Full job description including responsibilities, requirements, and nice-to-haves',
            },
            stack: {
              type: 'string',
              description: 'Required tech stack, comma-separated (e.g. "Node.js,TypeScript,AWS")',
            },
            comp_band: {
              type: 'string',
              description: 'Compensation band (e.g. "$120k–$160k", "€80k–€110k")',
            },
          },
          required: ['title', 'description', 'stack', 'comp_band'],
        },
      },
      {
        name: 'update_application_stage',
        description: 'Move a job application to a new stage in the hiring pipeline.',
        inputSchema: {
          type: 'object',
          properties: {
            application_id: {
              type: 'string',
              description: 'Application ID to update',
            },
            stage: {
              type: 'string',
              enum: ['applied', 'screening', 'interview', 'technical', 'offer', 'accepted', 'rejected', 'withdrawn'],
              description: 'New pipeline stage for the application',
            },
          },
          required: ['application_id', 'stage'],
        },
      },
    ];
  • Handler for tools/call that proxies tool invocations to the backend. Since track_application is in NEW_TOOL_NAMES (line 241), if the backend is unreachable, a stub response with 'not_implemented' status is returned (lines 283-300). The actual implementation lives on the backend server.
    async function handleToolsCall(id, params) {
      const toolName = params && params.name;
    
      try {
        const result = await callBackend({ jsonrpc: '2.0', id, method: 'tools/call', params });
        send({ ...result, id });
      } catch (err) {
        // If the backend is unreachable and this is a new tool, return a clear stub message
        if (NEW_TOOL_NAMES.has(toolName)) {
          send({
            jsonrpc: '2.0',
            id,
            result: {
              content: [
                {
                  type: 'text',
                  text: JSON.stringify({
                    status: 'not_implemented',
                    tool: toolName,
                    message: `The '${toolName}' tool is defined in the MCP layer but the backend handler is not yet deployed. Backend error: ${err.message}`,
                  }, null, 2),
                },
              ],
              isError: false,
            },
          });
        } else {
          send({ jsonrpc: '2.0', id, error: { code: -32000, message: err.message } });
        }
      }
    }
Behavior3/5

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

No annotations exist, so description alone must convey behavior. It implies a read operation ('Get') but does not explicitly state it is read-only or mention any side effects, authentication requirements, or rate limits. Adequate but minimal.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single concise sentence of 12 words. Every word is necessary, no redundancy.

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 simple tool with one required parameter and no output schema, the description covers the essential purpose and input. However, it does not describe the return format, which could be useful 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?

Schema coverage is 100% for the single parameter. The description adds no additional meaning beyond what is in the schema; it merely restates that the tool looks up by 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 clearly specifies the action (Get), the resource (current status and details of a job application), and the required input (application_id). It is distinct from sibling tools like list_job_applications or update_application_stage.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives such as list_job_applications or get_application_analytics. The description assumes the user knows to provide an ID but does not help in tool selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Exidian-Tech/placed-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server