Skip to main content
Glama

Apply to several job listings

applyToJobs
Destructive

Send the candidate's application to several job board listings in one go (up to 50), each the same way applyToJob sends one: Clera fills each employer's form from their profile with the resume tailored to that role when there is one, otherwise their primary resume, and sends it only when every required field is filled. Run it only when the candidate has named the roles to apply to; pass each jobId with position and companyName exactly as searchJobs or readJobListing (kind board) gave them, and a mismatch refuses the whole call.

The candidate gets one confirmation listing every role before anything is sent. Closed postings, roles they already applied to, and anything past their auto-apply runs left today come back with a refusedReason instead of a runId. Every started one has its own runId: check each with getApplicationRun. Runs that need answers come back needs_input with nothing sent; answer those one at a time with applyToJob. Always submit mode; for a dry run use applyToJob.

Clera privately records this tool's inputs and results for usage tracking and support.

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": {
      "jobs": "<jobs>"
    },
    "name": "applyToJobs"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobsYesThe listings to apply to, each one the candidate asked for.
confirmSubmitNoOnly when your client cannot show the confirmation prompt: "submit" once the candidate has said yes to sending these applications, "cancel" otherwise. Never set it on your own.

Output Schema

NameRequiredDescriptionDefault
refusedYes
resultsYes
startedYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.8/5.0
Behavior5/5

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

Annotations declare destructive/openWorld/non-idempotent, and the description adds context the annotations cannot: a pre-send confirmation listing every role, partial-failure semantics (refusedReason for closed postings, prior applications, exhausted auto-apply runs), per-run runId tracking, and an explicit no-send guarantee for needs_input. It also discloses the data-recording practice, which is exactly the kind of side effect an agent cannot infer.

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?

Three tight paragraphs that are front-loaded with the core action and the batch/singular distinction, and every sentence carries operational weight. The closing privacy sentence is boilerplate but short, and the middle paragraph is dense enough that it earns its length.

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 destructive, open-world batch mutation with an output schema, the definition covers the confirmation gate, failure modes, per-item run tracking, and the delegation path for follow-ups. Nothing an agent needs in order to invoke it safely is missing, and return-value structure is left to the output schema as intended.

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, but the description adds real meaning: jobId/position/companyName must be copied verbatim from searchJobs or readJobListing (kind board) and any mismatch refuses the entire call, which is a validation rule absent from the schema. It also constrains confirmSubmit to clients that cannot render the confirmation prompt and forbids setting it autonomously.

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 ("Send the candidate's application to several job board listings in one go, up to 50") and immediately distinguishes itself from the singular applyToJob by describing the batch semantics. An agent can tell the two apart without opening either 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?

Explicit gating condition ("Run it only when the candidate has named the roles to apply to"), explicit alternative for dry runs ("for a dry run use applyToJob"), and explicit handoff for the needs_input case ("answer those one at a time with applyToJob"). It also names getApplicationRun as the follow-up for each runId, so routing in and out of the tool is fully specified.

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