Skip to main content
Glama

Check a job posting

check_job_posting
Read-onlyIdempotent

Checks whether one employer job posting is still open, for questions like “is this job still taking applications?”: url is the https link to the employer's posting. Returns open, closed, unknown (a posting Applystead does not track) or unsupported (not a posting link Applystead reads), as of Applystead's last read (the link itself is not fetched), with a tracked posting's title, company and Applystead job page, and an open one's listed pay and Apply with Applystead link. Apply with Applystead opens an Applystead account that tailors a résumé to a job and prepares applications for the person.

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": {
      "url": "<url>"
    },
    "name": "check_job_posting"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe https link to the employer's job posting.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the readOnly/idempotent/openWorld annotations, the description discloses the complete result taxonomy (open, closed, unknown, unsupported), explains that results reflect Applystead's last read rather than a live fetch, and clarifies what data accompanies tracked and open postings. It also explains the 'Apply with Applystead' link's downstream effect of creating an account, which is significant context an agent should know before presenting that option.

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 core purpose is front-loaded, followed by return values and contextual explanation. However, the second sentence is a long, clause-heavy run-on, and the 'Apply with Applystead' concept is explained twice in close proximity, which slightly reduces efficiency.

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?

There is no output schema, so the description must fully explain return values, and it does: it enumerates all four statuses, describes accompanying fields for tracked and open postings, and clarifies staleness. Combined with the input schema's complete url documentation and the read-only annotations, an agent has everything needed to call and interpret this tool correctly.

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 url parameter, and the description largely restates what the schema already says: an https link to the employer's posting. It adds slight nuance by emphasizing 'one employer job posting' and the https constraint, but does not provide format examples or edge-case guidance beyond the schema. Baseline 3 is appropriate.

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?

States a specific verb and resource: 'Checks whether one employer job posting is still open.' This clearly distinguishes it from discovery-oriented siblings like search_jobs, get_jobs, and get_company_jobs, which list or find postings rather than checking a single URL's 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?

The description gives a concrete usage context ('for questions like "is this job still taking applications?"') and defines the input as an https link to the employer's posting. It does not explicitly name alternatives such as get_jobs or search_jobs or state when not to use this tool, so it falls short of full alternative routing.

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.