Skip to main content
Glama

apply_to_job

Submit a job application, create a tracker entry with APPLIED status, and optionally auto-generate a cover letter.

Instructions

Apply to a job — creates a job tracker entry with status APPLIED and optionally generates a cover letter.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
candidate_idNoUser/candidate ID (optional, defaults to authenticated user)
job_idNoJob ID to apply to
companyYesCompany name
positionYesJob title / position
job_urlNoURL of the job posting (optional)
job_descriptionNoFull job description text (optional)
cover_letterNoCover letter text. If omitted, one will be auto-generated.
resume_idNoResume ID to attach to this application (optional)

Implementation Reference

  • index.js:154-176 (registration)
    The tool 'apply_to_job' is registered in the WEEK2_TOOLS array with its name, description, and inputSchema definition.
    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'],
        },
      },
  • Input schema for apply_to_job: requires candidate_id and job_id, optional cover_letter.
    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'],
    },
  • The handler for tools/call: all tools (including apply_to_job) are proxied to the backend via callBackend(). If the backend is unreachable and the tool is a new tool, a 'not_implemented' stub response is returned.
    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 } });
        }
      }
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden. It mentions that a tracker entry is created and cover letter generation is optional, but lacks details on side effects, authorization requirements, or whether the application is actually submitted externally.

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?

The description is a single, concise sentence that conveys the essential purpose without any unnecessary words or repetition. It is front-loaded and efficient.

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

Completeness2/5

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

Given the tool has 8 parameters, 2 required, no output schema, and no annotations, the description is too brief. It omits important context such as how optional parameters (job_url, resume_id) are used, whether the application is actually submitted, and the nature of the tracker entry.

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?

The input schema has 100% coverage with descriptions for all 8 parameters, so the description adds only marginal value. It explains the cover_letter parameter's auto-generation behavior, but otherwise does not enrich understanding beyond the schema.

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?

The description clearly states the tool's action: applying to a job, creating a tracker entry, and optionally generating a cover letter. However, it does not differentiate from sibling tools like 'add_job_application' or 'track_application', leaving ambiguity about when to use this specific tool.

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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, exclusions, or scenarios where another tool might be more appropriate.

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