[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# Screen new JobAdder applicants with AI

> Rate new JobAdder applications out of 5 against your brief, reject clear mismatches and keep edge cases for you. Runs daily, hosted.

Source: https://cotlet.dev/integrations/jobadder-api-mcp-server/screen-job-applicants

A job ad goes up on several boards, applications land in JobAdder overnight, and every morning a recruiter opens each one to decide whether it deserves a call.

Cotlet does it in your own JobAdder account with list\_job\_applications, get\_candidate, rate\_application and update\_application\_status, called by your AI agent, an n8n workflow or a script.

[Sign up free](https://cotlet.dev/app/signup?app=jobadder) [All JobAdder tools](https://cotlet.dev/integrations/jobadder-api-mcp-server.md)

Hosted · nothing to install or maintain

## Can JobAdder do this on its own?

JobAdder ranks and summarises candidates with its own tools (Candidate matching, Smart Summary), and a status update can trigger actions (checked 22 Oct 2026). Applying your own written criteria to each applicant and recording the reason is still done by hand, and from code it needs API access that JobAdder grants by approval.

## How you do it in JobAdder today

1. JobAdder puts an applicant dashboard in the Home tab, where a recruiter can review the applicant stages, change statuses, add notes and message candidates.
2. Each application opens in a quick view popup that shows the candidate's previous applications, so a returning applicant is easy to spot.
3. The recruiter gives the application a rating out of 5 and selects the applicant's status; JobAdder can trigger actions with a status update and supports custom rejection statuses.
4. In the mobile app a swipe left on the applicant's card rejects, and a swipe right progresses.
5. Every applicant is read one by one, so a role that draws many applications takes a full sitting to clear.

## How to screen new JobAdder applicants with AI

Prompt

```
List the new applications on the Senior Accountant job in JobAdder. Rate each out of 5 against my brief, reject the clear mismatches and leave the rest for me with a one-line reason.
```

1. 01  
### Pull the applications  
list\_job\_applications returns the applications of one job with the candidate name, current status and rating. The agent follows next\_cursor until the list ends, so a large intake is judged as one batch.
2. 02  
### Read the ones that are not obvious  
get\_candidate brings the profile, skills and employment history of each applicant who needs a closer look. Applicants who clearly miss a must-have in your brief are decided from the list alone.
3. 03  
### Apply your brief  
The agent compares each applicant with the must-haves and nice-to-haves from your prompt, for example "CPA licence" or "five years in a mid-size firm". It quotes the line it relied on, so you see why each person scored as they did.
4. 04  
### Rate every applicant  
rate\_application sets the rating out of 5 on each application. A rating reaches nobody and is changed with one more call, so it does not wait for your OK.
5. 05  
### Reject only the clear mismatches  
update\_application\_status moves clear mismatches to the rejection status you named. It waits for your OK, because in JobAdder a status update can trigger an action such as an automatic reply, depending on your setup. A status the job's workflow does not have makes the call fail, and the agent lists that applicant for you instead.
6. 06  
### Leave the middle to you  
Applicants in the grey zone keep their status and come back in one list, each with the rating and a one-line reason.

### What you get back

Example data

```
Applications on Senior Accountant: 17
Rated 4 or 5: 5, e.g. Priya Nair: "CPA, six years in a mid-size firm"
Rejected 8 (no accounting licence, outside the location in the brief)
Left for you 4:
- Daniel Moore: strong skills, two-month notice period
- Lena Fischer: licence pending
```

### Other ways to ask

- Every morning at 7, rate new applications on every open job and send me the ones rated 4 or 5.
- Rate the applications but change no status, and list the ones I should call first.
- Reject applicants whose profile misses the licence in the brief, and show me the list before anything changes.
- Compare the five best applicants on this job in a table.

## What JobAdder allows, and what to know first

- JobAdder lets recruiters give each application a rating out of 5, so the score the agent sets sits where your team already looks.
- JobAdder can trigger actions with a status update and supports custom rejection statuses, so the status the agent sets should be the one your workflow uses for a rejection.
- JobAdder's own platform note recommends that auto-response emails with a delayed send do not apply a status change, so check how your templates behave before the agent rejects in bulk.
- A JobAdder form submitted against a job creates an Application record automatically, so applicants from your own forms appear in the same list as board applicants.

update\_application\_status asks for your OK by default. To run it daily without you, switch confirmation off for that tool in your dashboard.

Sources: [JobAdder: Applicant Tracking System](https://jobadder.com/applicant-tracking/) · [JobAdder: Platform updates](https://jobadder.com/platform-updates/page/6/) · [JobAdder: Forms](https://jobadder.com/platform-feature/smart-forms/)

## Call rate\_application from a script

curl

```
curl -X POST https://cotlet.dev/api/v1/jobadder/applications/app_48213/rate \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"rating":4}'
```

Example response

```
{
"application_id": "app_48213",
"rating": 4
}
```

MCP: add https://cotlet.dev/mcp/v1 with the same key; the call is jobadder\_write → rate\_application. Example data.

[Schedule it in n8n, Make, Zapier or cron](https://cotlet.dev/integrations/jobadder-api-mcp-server.md#automations)

## JobAdder tools this automation uses

__Cotlet JobAdder tools used to screen new JobAdder applicants with AI__
| Tool | Parameters |
| --------------------------- | ------------------------------ |
| list\_job\_applications | job\_id, status, limit, cursor |
| get\_candidate | candidate\_id |
| rate\_application | application\_id, rating |
| update\_application\_status | application\_id, status |

[All 12 JobAdder tools with descriptions](https://cotlet.dev/integrations/jobadder-api-mcp-server.md#tools)

## Frequently asked questions

### Is it safe to connect JobAdder to Cotlet?

Yes. You sign in to JobAdder yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get JobAdder once you enable it, every background request is listed, and the browser profile is stored encrypted with AES-256-GCM, the cipher 1Password uses for its vaults. The AI model never sees a login, posts and messages wait for your OK, and Disable for agents cuts access in one click. Independent scanners grade cotlet.dev A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory; live results are on https://cotlet.dev/security.

## More JobAdder automations

- [Log call notes on JobAdder candidate records](https://cotlet.dev/integrations/jobadder-api-mcp-server/log-call-notes.md)
- [JobAdder API and MCP server: every tool](https://cotlet.dev/integrations/jobadder-api-mcp-server.md)
- [All use cases](https://cotlet.dev/use-cases.md)

## Give your agent access to JobAdder.

Free 7-day trial with 2,000 credits, no card needed. Cotlet is independent and not affiliated with JobAdder.

[Sign up free](https://cotlet.dev/app/signup?app=jobadder)

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.

## For AI agents: sign your user up

Is your user asking you to sign them up for Cotlet? You can do it for them, no account or key needed.

1. Read the fields and their allowed values: GET https://cotlet.dev/api/v1/access-requests
2. Ask the user for each value: email, apps, what you will do with them. If they leave the password to you, generate a strong one and show it to them.
3. Show the user what you will send, then POST it as JSON to https://cotlet.dev/api/v1/access-requests.

One call creates the account and sends the access request; we email the user when access is granted.