Skip to main content
Glama

Read a job posting link

read_job_link
Read-only

Read a link to a job posting into its title, company, location and full text. Spends no analysis. Postings on Greenhouse, Lever, Ashby, SmartRecruiters, Workday, Workable and Recruitee are read through the board's public API, which also says whether the posting is still open; other links come from a copy a radar already saved (source=pool; open_confirmed_at null means nobody confirmed it is still open) or from the page through the job posting it declares or its main text; partial=true means only a board's short summary could be had. The text goes to analyze_vacancy as description, with title, company, location and url; existing_analysis_id means this user already analyzed the link and get_vacancy_detail shows that analysis. A link that gives no posting comes back with unavailable set to the reason: posting_closed, blocked, unreadable, or login_required (LinkedIn and Glassdoor pages are not read). Errors: rate_limited (20 links an hour, 10 a day on the free plan, 60 on a paid one; a link the user already analyzed is not counted), invalid_payload.

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": {
      "input": "<input>"
    },
    "name": "read_job_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYes

Output Schema

NameRequiredDescriptionDefault
urlYesThe link, cleaned of tracking parameters.
titleNoThe posting's title as the page or the job board names it.
sourceNoWhere the text came from: ats = the job board's public API, read now; page = the page itself, read now; pool = a copy a radar saved when it found the posting, used where the board has no public API or it did not answer.
companyNoThe employer, when the posting names one.
partialNoTrue when the text is only a board's short summary: the page itself gave nothing longer.
locationNoWhere the job is, as the posting says it.
captured_atNoWhen the text was taken from its source (UTC, ISO 8601): for pool, when a radar found the posting; for ats and page, when it was read, up to a day ago for a link read recently.
descriptionNoThe posting's full text, up to 20 000 characters.
unavailableNoWhy the link gave no posting; null when it was read. posting_closed = the site answered that the page does not exist (404/410) or the board lists the posting as closed: the job was filled, moved or never existed, and these cases look the same; blocked = the site refused to show the page to a reader; login_required = the site shows its postings only to signed-in visitors; unreadable = the page did not answer or holds no readable posting. In the last three cases the posting text has to be pasted. When set, the posting text is empty and url is the link as given; nothing was spent. title and existing_analysis_id still name this user's analysis of the link when there is one.
open_confirmed_atNoWhen the job board last answered that the posting is open (UTC, ISO 8601): for ats, when its API served it; for pool, the radar's nightly check of a kept match. Null means openness is not confirmed, not that the posting is open: a page and most pool copies are never checked, and the posting may have closed since captured_at.
existing_analysis_idNoThis user's analysis of the same link, when there is one; get_vacancy_detail shows it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / open_confirmed_at
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "When the job board last answered that the posting is open (UTC, ISO 8601): for ats, when its API served it; for pool, the radar's nightly check of a kept match. Null means openness is not confirmed, not that the posting is open: a page and most pool copies are never checked, and the posting may have closed since captured_at.",
      +  "title": "Open Confirmed At"
      +}
    • changedOutput schema / properties / source / description
      Previous value: -"Where the text came from: ats = the job board's public API, read now; page = the page itself, read now; pool = a copy a radar saved when it found the posting, not a check that the posting is still open — pool is used where the board has no public API or it did not answer, and the site may have closed the posting since captured_at."New value: +"Where the text came from: ats = the job board's public API, read now; page = the page itself, read now; pool = a copy a radar saved when it found the posting, used where the board has no public API or it did not answer."
  2. Changed3 schema fields changed
    • addedOutput schema / properties / captured_at
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "When the text was taken from its source (UTC, ISO 8601): for pool, when a radar found the posting; for ats and page, when it was read, up to a day ago for a link read recently.",
      +  "title": "Captured At"
      +}
    • changedOutput schema / properties / source / description
      Previous value: -"Where the text came from: pool = a posting the user's or another radar already found, ats = the job board's public API, page = the page itself."New value: +"Where the text came from: ats = the job board's public API, read now; page = the page itself, read now; pool = a copy a radar saved when it found the posting, not a check that the posting is still open — pool is used where the board has no public API or it did not answer, and the site may have closed the posting since captured_at."
    • changedOutput schema / properties / unavailable / description
      Previous value: -"Why the link gave no posting; null when it was read. posting_closed = the page is gone or the board lists the posting as closed; blocked = the site refused to show the page to a reader; login_required = the site shows its postings only to signed-in visitors; unreadable = the page did not answer or holds no readable posting. In the last three cases the posting text has to be pasted. When set, the posting fields are empty and url is the link as given; nothing was spent."New value: +"Why the link gave no posting; null when it was read. posting_closed = the site answered that the page does not exist (404/410) or the board lists the posting as closed: the job was filled, moved or never existed, and these cases look the same; blocked = the site refused to show the page to a reader; login_required = the site shows its postings only to signed-in visitors; unreadable = the page did not answer or holds no readable posting. In the last three cases the posting text has to be pasted. When set, the posting text is empty and url is the link as given; nothing was spent. title and existing_analysis_id still name this user's analysis of the link when there is one."
  3. Changed8 schema fields changed
    • addedOutput schema / properties / description / default
      Added value: +""
    • addedOutput schema / properties / source / anyOf
      Added value: +[
      +  {
      +    "enum": [
      +      "pool",
      +      "ats",
      +      "page"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • addedOutput schema / properties / source / default
      Added value: +null
    • removedOutput schema / properties / source / enum
      Removed value: -[
      -  "pool",
      -  "ats",
      -  "page"
      -]
    • removedOutput schema / properties / source / type
      Removed value: -"string"
    • addedOutput schema / properties / title / default
      Added value: +""
    • addedOutput schema / properties / unavailable
      Added value: +{
      +  "anyOf": [
      +    {
      +      "enum": [
      +        "posting_closed",
      +        "blocked",
      +        "login_required",
      +        "unreadable"
      +      ],
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Why the link gave no posting; null when it was read. posting_closed = the page is gone or the board lists the posting as closed; blocked = the site refused to show the page to a reader; login_required = the site shows its postings only to signed-in visitors; unreadable = the page did not answer or holds no readable posting. In the last three cases the posting text has to be pasted. When set, the posting fields are empty and url is the link as given; nothing was spent.",
      +  "title": "Unavailable"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "title",
      -  "description",
      -  "url",
      -  "source"
      -]New value: +[
      +  "url"
      +]
  4. Changed1 schema field changed
    • addedOutput schema / properties / partial
      Added value: +{
      +  "default": false,
      +  "description": "True when the text is only a board's short summary: the page itself gave nothing longer.",
      +  "title": "Partial",
      +  "type": "boolean"
      +}
  5. Added

TDQS

A4.2/5.0
Behavior2/5

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

The disclosure itself is unusually rich: per-board public APIs, pool fallback semantics, the partial flag, the four unavailable reasons, the existing_analysis_id signal, and concrete rate limits (20/hour, 10/day free, 60 paid) with a dedup exception. However, the description's own content — fetching arbitrary external posting pages, handling blocked/login_required responses, excluding LinkedIn/Glassdoor — conflicts with the annotation openWorldHint=false, since this tool plainly reaches into an open external world; that mismatch undercuts how far the annotations can be trusted alongside the text.

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?

Front-loaded correctly: purpose and the 'no analysis' distinction come first, followed by source behavior, then error conditions. It is dense and parenthetical-heavy ('source=pool; open_confirmed_at null means nobody confirmed it is still open'), which costs readability, but every clause carries operational information rather than filler.

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?

For a one-parameter, one-external-call tool this is essentially complete: source resolution, fallbacks, partial results, failure reasons, downstream routing, and error codes with exact rate-limit numbers are all given. An output schema exists, so the description is not obliged to restate return shapes, and the output flags it does mention are the ones that change agent decisions.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is effectively one input (url) and the schema only says 'Link to a job posting page.' The description adds real domain meaning: which hosts are read via public APIs, which hosts are refused entirely, and which URL classes fall through to a saved copy or page scraping. It stops short of format constraints (e.g. scheme or canonicalization), so not quite a 5.

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 first sentence states a specific verb and resource plus the exact payload returned: 'Read a link to a job posting into its title, company, location and full text.' The follow-up 'Spends no analysis' and the handoff to analyze_vacancy / get_vacancy_detail make it distinguishable from the sibling analysis tools without opening their schemas.

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?

It routes the agent explicitly: this tool extracts text only, the text 'goes to analyze_vacancy as description', and existing_analysis_id means you should look at get_vacancy_detail instead. It also states when-not boundaries — LinkedIn and Glassdoor pages are not read, and unavailable reasons explain failed cases — leaving nothing to inference.

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.