Skip to main content
Glama

Worklittle Jobs

Jobs · Apply For Job

apply_for_job
Destructive

Jobs — Apply to jobs for the user: Worklittle fills out and submits each application. Pass job_id from search_jobs, or job_ids (up to 10) when they want to apply to several or all of them at once. Worklittle-hosted postings work the same way: their form is filled from the user's profile. It submits by default; pass auto_submit false when the user wants to review first, then show them the answers from check_application_status and send it with submit_application only after they say so. If it answers RESUME_REQUIRED or resume_warning, the user has no résumé saved: follow next_step (upload theirs with upload_my_resume, or write one with create_resume and save_to_profile true) and apply again.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "apply_for_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoInstead of job_id: a link to the job posting (the employer's job page or application page), when the user pastes one. Worklittle finds the job, or adds it if it isn't listed, and applies; the result includes its job_id. If it can't apply through the link, the error says why and lists similar_jobs.
testNotrue: a free practice run. Nothing opens, nothing is stored or sent to an employer, no personal information needed. The session moves queued → running → completed over ~25 seconds.
urlsNoLike job_ids, for job posting links (can be combined with job_ids, up to 10 jobs in all). Each result includes its url and job_id.
job_idNoWorklittle job id from search_jobs / get_job_details.
job_idsNoApply to up to 10 jobs in one call (instead of job_id), all for the same person and with the same options. Returns one result per job.
applicantNoWith use_profile false: the person applying. name and email are required; phone, city, state, country, work_authorization, needs_sponsorship, desired_salary, about_you are recommended. Send their resume as resume_text or resume_pdf_base64.
resume_idNoUse this one of the user's saved resumes. Leave out to let Worklittle pick the best one for the job.
auto_submitNoDefault: the user's auto_submit setting (on unless they turned it off), which submits when the form is complete. false: stop at review (status awaiting_submit) so the user can check every answer; send it with submit_application.
resume_htmlNoOptional resume HTML to seed.
resume_textNoWith use_profile false: the applicant's resume as plain text.
use_profileNoDefault true: apply as the signed-in user with their profile. false: apply as the applicant described below (another person, no Worklittle account needed).
applicant_idNoWith use_profile false: the person from an earlier apply. Store it permanently with the person and reuse it; it works with any Worklittle API key. It is also emailed to them; if lost, ask them for it.
tailor_resumeNoDefault from apply settings (on): write a resume tailored to this job. false: send the resume as is.
max_per_companyNoApplications to one company per 30 days for this person. Defaults to their apply setting (3). Raise it only after the person agrees, when a start returned COMPANY_LIMIT_REACHED.
cover_letter_htmlNoOptional cover letter HTML to seed.
resume_pdf_base64NoWith use_profile false: the applicant's resume PDF, base64.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / url
      Added value: +{
      +  "description": "Instead of job_id: a link to the job posting (the employer's job page or application page), when the user pastes one. Worklittle finds the job, or adds it if it isn't listed, and applies; the result includes its job_id. If it can't apply through the link, the error says why and lists similar_jobs.",
      +  "type": "string"
      +}
    • addedInput schema / properties / urls
      Added value: +{
      +  "description": "Like job_ids, for job posting links (can be combined with job_ids, up to 10 jobs in all). Each result includes its url and job_id.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
  2. Changed1 schema field changed
    • changedInput schema / properties / auto_submit / description
      Previous value: -"Default true: submit when the form is complete. false: stop at review (status awaiting_submit) so the user can check every answer; send it with submit_application."New value: +"Default: the user's auto_submit setting (on unless they turned it off), which submits when the form is complete. false: stop at review (status awaiting_submit) so the user can check every answer; send it with submit_application."
  3. Changed2 schema fields changed
    • removedInput schema / properties / confirm_same_company
      Removed value: -{
      -  "description": "Only after the person agrees: apply even though they already applied to 3+ jobs at this company in the last 30 days (the call paused with CONFIRM_SAME_COMPANY).",
      -  "type": "boolean"
      -}
    • addedInput schema / properties / max_per_company
      Added value: +{
      +  "description": "Applications to one company per 30 days for this person. Defaults to their apply setting (3). Raise it only after the person agrees, when a start returned COMPANY_LIMIT_REACHED.",
      +  "maximum": 10,
      +  "minimum": 1,
      +  "type": "integer"
      +}
  4. Changed1 schema field changed
    • changedInput schema / properties / applicant_id / description
      Previous value: -"With use_profile false: the person from an earlier apply. Store it permanently with the person and reuse it. It is also emailed to them; if lost, ask them for it."New value: +"With use_profile false: the person from an earlier apply. Store it permanently with the person and reuse it; it works with any Worklittle API key. It is also emailed to them; if lost, ask them for it."
  5. Changed1 schema field changed
    • changedInput schema / properties / applicant_id / description
      Previous value: -"With use_profile false: reuse an applicant from an earlier apply."New value: +"With use_profile false: the person from an earlier apply. Store it permanently with the person and reuse it. It is also emailed to them; if lost, ask them for it."
  6. Changed1 schema field changed
    • addedInput schema / properties / confirm_same_company
      Added value: +{
      +  "description": "Only after the person agrees: apply even though they already applied to 3+ jobs at this company in the last 30 days (the call paused with CONFIRM_SAME_COMPANY).",
      +  "type": "boolean"
      +}
  7. Changed10 schema fields changed
    • addedInput schema / properties / applicant
      Added value: +{
      +  "description": "With use_profile false: the person applying. name and email are required; phone, city, state, country, work_authorization, needs_sponsorship, desired_salary, about_you are recommended. Send their resume as resume_text or resume_pdf_base64.",
      +  "properties": {
      +    "about_you": {
      +      "description": "Standing answers: notice period, sponsorship, referrals, anything else.",
      +      "type": "string"
      +    },
      +    "city": {
      +      "type": "string"
      +    },
      +    "country": {
      +      "type": "string"
      +    },
      +    "desired_salary": {
      +      "type": "string"
      +    },
      +    "email": {
      +      "type": "string"
      +    },
      +    "linkedin": {
      +      "type": "string"
      +    },
      +    "name": {
      +      "type": "string"
      +    },
      +    "needs_sponsorship": {
      +      "description": "true if they need visa sponsorship to work",
      +      "type": "boolean"
      +    },
      +    "phone": {
      +      "type": "string"
      +    },
      +    "state": {
      +      "type": "string"
      +    },
      +    "website": {
      +      "type": "string"
      +    },
      +    "work_authorization": {
      +      "description": "ISO2 country codes",
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "name",
      +    "email"
      +  ],
      +  "type": "object"
      +}
    • addedInput schema / properties / applicant_id
      Added value: +{
      +  "description": "With use_profile false: reuse an applicant from an earlier apply.",
      +  "type": "string"
      +}
    • addedInput schema / properties / job_ids
      Added value: +{
      +  "description": "Apply to up to 10 jobs in one call (instead of job_id), all for the same person and with the same options. Returns one result per job.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / resume_id
      Added value: +{
      +  "description": "Use this one of the user's saved resumes. Leave out to let Worklittle pick the best one for the job.",
      +  "type": "string"
      +}
    • addedInput schema / properties / resume_pdf_base64
      Added value: +{
      +  "description": "With use_profile false: the applicant's resume PDF, base64.",
      +  "type": "string"
      +}
    • addedInput schema / properties / resume_text
      Added value: +{
      +  "description": "With use_profile false: the applicant's resume as plain text.",
      +  "type": "string"
      +}
    • addedInput schema / properties / tailor_resume
      Added value: +{
      +  "description": "Default from apply settings (on): write a resume tailored to this job. false: send the resume as is.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / test
      Added value: +{
      +  "description": "true: a free practice run. Nothing opens, nothing is stored or sent to an employer, no personal information needed. The session moves queued → running → completed over ~25 seconds.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / use_profile
      Added value: +{
      +  "description": "Default true: apply as the signed-in user with their profile. false: apply as the applicant described below (another person, no Worklittle account needed).",
      +  "type": "boolean"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "job_id"
      -]New value: +[]
  8. Changed1 schema field changed
    • changedInput schema / properties / auto_submit / description
      Previous value: -"Ignored on API keys. Sessions started with a key always submit."New value: +"Default true: submit when the form is complete. false: stop at review (status awaiting_submit) so the user can check every answer; send it with submit_application."
  9. Changed1 schema field changed
    • changedInput schema / properties / auto_submit / description
      Previous value: -"If false, wait for approve_apply_submit before submitting. Default true (always submit on)."New value: +"Ignored on API keys. Sessions started with a key always submit."
  10. Added

TDQS

A4.5/5.0
Behavior4/5

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

Adds substantial context beyond the annotations: it submits by default, defaults to review only when auto_submit is false, Worklittle-hosted postings use the profile, and RESUME_REQUIRED/resume_warning should be resolved via next_step then retried. The main gap is that it never warns about duplicate applications — annotations mark this non-idempotent and destructive, so an agent retrying after a timeout has no guidance on whether the first application already went out.

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 with the core action and one-call-many-jobs rule, then the review flow, then error recovery — a sensible ordering. It is a single dense paragraph, though, and the résumé-error recovery sentence packs several steps together, so it reads slightly heavier than necessary.

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 16-parameter, open-world, destructive tool with an output schema, it covers the critical paths: batching, review-before-submit, and résumé-missing recovery via next_step. What is missing is retry/idempotency guidance and any note about per-person company limits beyond the schema's own max_per_company entry.

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 still adds value by explaining the interaction between job_id/job_ids/url (up to 10 jobs in one call) and by spelling out the auto_submit=false → awaiting_submit → submit_application sequence, which is behavioral meaning the schema alone does not convey.

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 concrete verb and resource ('Apply to jobs for the user'), plus the mechanism ('Worklittle fills out and submits each application'). It also distinguishes itself from the review path (submit_application) and the lookup path (search_jobs), so an agent can pick it without opening the schema.

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?

Gives explicit routing rules: job_id from search_jobs, job_ids for up to 10 at once, url when the user pastes a link, and auto_submit false when the user wants to review before sending. It names the alternatives (check_application_status, submit_application, upload_my_resume, create_resume) with the conditions that select them.

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.

Resources