Skip to main content
Glama

post_job

Create a new job listing as an employer, adding it to the tracker with title, description, tech stack, compensation, and company details.

Instructions

Post a new job listing (employer-side). Creates a job entry in the tracker as an employer-posted listing.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesJob title
descriptionYesFull job description
stackYesRequired tech stack (comma-separated)
comp_bandNoCompensation band
locationNoJob location or 'Remote'
companyNoCompany name

Implementation Reference

  • Input schema definition for the post_job tool, specifying required fields: title, description, stack, comp_band.
      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'],
      },
    },
  • index.js:191-216 (registration)
    Tool registration in the WEEK2_TOOLS array, defining the tool name 'post_job' and its input schema.
    {
      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'],
      },
    },
  • Handler for tool calls: handleToolsCall proxies all tool calls (including post_job) to the backend via callBackend(). Since the backend handler is not yet deployed, it returns a 'not_implemented' stub.
    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, the description should disclose behavioral traits like authentication requirements, side effects, or constraints. It only states it creates an entry, omitting important details like duplicate handling or permission needs.

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 two concise sentences that front-load the core purpose. Every word adds value without unnecessary elaboration.

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?

The tool has a moderate complexity (6 parameters, nested objects) and no output schema. The description should clarify what the tool returns (e.g., a job ID) or any post-condition, but it does not.

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% description coverage, so the baseline is 3. The description does not add additional meaning beyond what the schema already provides for each parameter.

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 states the tool's purpose: 'Post a new job listing (employer-side)' and explains it creates a job entry. It distinguishes from sibling tools like search_jobs and apply_to_job, which are for different user roles.

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 description mentions 'employer-side' to imply usage context but does not explicitly state when to use or avoid this tool, nor does it reference alternative tools like apply_to_job for job seekers.

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