Skip to main content
Glama

get_job

Retrieve comprehensive details for a specific job posting, including description, salary, skills, and company information, using the job listing ID.

Instructions

Get detailed information about a specific job listing/posting by its job listing ID (not application ID). Use this to view the full job posting details including description, salary, skills, and company info. For job application details, use get_application instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe job ID

Implementation Reference

  • The implementation of the 'get_job' tool, which takes a job ID as an argument and fetches detailed information from the API client.
    server.tool(
      'get_job',
      'Get detailed information about a specific job listing/posting by its job listing ID (not application ID). Use this to view the full job posting details including description, salary, skills, and company info. For job application details, use get_application instead.',
      {
        id: z.string().describe('The job ID'),
      },
      async (args) => {
        const job = await client.getJob(args.id);
        return { content: [{ type: 'text' as const, text: JSON.stringify(formatJob(job), null, 2) }] };
      }
    );
Behavior3/5

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

No annotations are provided, so the description carries full burden. It implies a read-only operation ('get', 'view') but doesn't explicitly state permissions, rate limits, or error behavior. It does add useful context about what information is returned (description, salary, skills, company info), which goes beyond basic purpose.

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?

Two sentences with zero waste. First sentence states purpose and key constraint. Second sentence provides usage guidance and alternative. Every word earns its place, and the most critical information is front-loaded.

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 read operation with 1 parameter and no output schema, the description is reasonably complete. It covers purpose, key constraint (ID type), usage guidance, and return content. However, without annotations or output schema, it could benefit from more behavioral details like error cases or response format.

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 description coverage is 100%, so the schema already documents the 'id' parameter. The description adds marginal value by clarifying it's a 'job listing ID (not application ID)', which helps disambiguate from similar identifiers, but doesn't provide format examples or constraints beyond what the schema implies.

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 verb 'get' and resource 'detailed information about a specific job listing/posting', specifying it's by 'job listing ID (not application ID)'. It distinguishes from sibling get_application by explicitly contrasting job posting details vs. application details.

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

Usage Guidelines5/5

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

Explicitly states when to use this tool ('to view the full job posting details') and when not to ('not application ID'), and provides a clear alternative ('use get_application instead'). This directly addresses sibling tool differentiation.

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/6figr-com/job-gpt-mcp-server'

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