Skip to main content
Glama

Fetch a job posting

freeapply_fetch_posting
Read-onlyIdempotent

Fetches a job posting from its URL and extracts the description, application questions, suggested answers, and required skills so you can score or apply before submitting the form.

Instructions

Fetches one job posting from the user's computer, trimmed: description, form questions, suggested answers, skills asked. Costs few tokens next to the browser, which you still use to fill and submit the form. Use: read each posting you found before scoring or applying. FreeApply has no job search of its own: search the user's job sites in the browser. Not for search-result or sign-in pages: read those in the browser. Behavior: read-only; one web request. Greenhouse, Lever, Ashby via their public APIs, other sites as page text. Public http(s) only: an address on this computer or a local network, or a redirect to one, is refused. Remembered this session, so freeapply_claim_job keeps its keywords. Parameters: url, the posting or its application form; max_chars caps only the description (default 6000, at least 500; description_chars tells you when it was cut); source, the job site where you found it (e.g. linkedin), picks the saved answers meant for that site. Returns: ats, title, company, location, work_mode, pay, description, description_chars (full length), questions [{label, required, type, options}], suggested_answers (from settings and saved answers; answer anything else only from the résumé or the user), keywords {matched, missing, coverage}: use matched in the posting's words, never claim missing; coverage = matched share in %, null if the posting names none. Errors: a bad or local address, or an unfetchable page, with the reason: read it in the browser. Next: freeapply_claim_job.

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": "freeapply_fetch_posting"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe job page or its application form.
sourceNoJob site id where found, e.g. linkedin.
max_charsNoDescription cap in characters (default 6000).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.6
    • changedInput schema / properties / source / description
      Previous value: -"Job site id where found, e.g. linkedin; picks the saved answers meant for that site."New value: +"Job site id where found, e.g. linkedin."
  2. Changed3 schema fields changedv1.0.4
    • changedInput schema / properties / max_chars / description
      Previous value: -"Longest description to return, in characters. Optional; default 6000."New value: +"Description cap in characters (default 6000)."
    • changedInput schema / properties / source / description
      Previous value: -"The job site id where it was found. Optional."New value: +"Job site id where found, e.g. linkedin; picks the saved answers meant for that site."
    • changedInput schema / properties / url / description
      Previous value: -"The posting's URL: the job page or its application form."New value: +"The job page or its application form."
  3. Changed1 schema field changedv1.0.2
    • changedInput schema / properties / source / description
      Previous value: -"Where the posting was found, as a job site id (linkedin, indeed, company_sites, ...). Optional; helps pick suggested answers."New value: +"The job site id where it was found. Optional."
  4. Changed5 schema fields changedv1.0.1
    • addedInput schema / properties / max_chars / default
      Added value: +6000
    • addedInput schema / properties / max_chars / description
      Added value: +"Longest description to return, in characters. Optional; default 6000."
    • addedInput schema / properties / max_chars / minimum
      Added value: +500
    • addedInput schema / properties / source / description
      Added value: +"Where the posting was found, as a job site id (linkedin, indeed, company_sites, ...). Optional; helps pick suggested answers."
    • addedInput schema / properties / url / description
      Added value: +"The posting's URL: the job page or its application form."
  5. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only cover read-only/idempotent/open-world, but the description adds substantive behavior: one web request, which sites use public APIs vs. page text, refusal of localhost/private-network addresses and redirects to them, and session-level caching so freeapply_claim_job retains keywords. It also specifies error behavior and recovery ("read it in the browser").

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?

Labeled sections (Use / Behavior / Parameters / Returns / Errors / Next) make it scannable and the critical routing guidance is front-loaded. It is long, and the token-cost aside ("Costs few tokens next to the browser...") is the least essential sentence, though it does reinforce the browser-vs-tool split.

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?

With no output schema and no annotations covering returns, the description fully carries that burden: it enumerates every returned field including items, suggested_answers provenance, and the keywords/coverage semantics with usage rules ("use matched in the posting's words, never claim missing"). Errors and the natural next tool are also documented.

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?

Schema coverage is 100% so the baseline is 3; the description goes beyond it by explaining that max_chars caps only the description and that description_chars signals truncation, and by explaining what `source` functionally does (selects saved answers for that site). The url semantics are merely restated ("the posting or its application form"), which is already in the schema.

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 ("Fetches one job posting") plus exactly what is returned (description, form questions, suggested answers, skills asked). It also disambiguates from siblings by naming freeapply_claim_job as the next step and clarifying that search happens in the browser, not here.

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?

Explicit when-to-use ("read each posting you found before scoring or applying") and explicit when-not ("Not for search-result or sign-in pages: read those in the browser"), plus the key constraint that FreeApply has no job search of its own. It routes to the correct alternative for the excluded cases.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.