Skip to main content
Glama

List tracked job applications

listApplications
Read-onlyIdempotent

List the jobs the candidate applied to or plans to apply to, from the external job board, a posting link or typed by hand: their job tracker, newest first, with each one's stage (draft, applied, assessment, ghosted, interview, offer, rejected), notes and links to any tailored resume (tailoredResume: draftId, fit before and after) or cover letter.

applicationState says where an applyToJob send stands (sending, sent, unconfirmed, needs_answers, not_sent, tracked); pendingQuestions are the employer's questions still waiting on the candidate. That is also how to pick up an application whose runId got lost: ask those questions and call applyToJob with its applicationId and answers. summary counts, across the whole board, what was sent and confirmed in the last 24 hours, what is sending, what was submitted but not confirmed, what needs the candidate's answers or OK, and what couldn't be sent; autoApplyRunsLeftToday is how many more applyToJob sends fit in the rolling 24 hours.

jobDescription is null here to keep the list small; readApplication returns one application with its full job description.

The job tracker also shows every Clera intro except withdrawn ones, but these tools only cover the jobs the candidate tracks themselves; listMyPipeline covers intros. Moving a card never contacts the company. Document links expire after an hour; list again for fresh ones.

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

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

Input Schema

NameRequiredDescriptionDefault
stageNoOnly return applications in this stage.
cursorNoPass nextCursor from a previous call to get the next page.

Output Schema

NameRequiredDescriptionDefault
hasMoreYes
summaryYes
nextCursorYes
applicationsYes
autoApplyRunsLeftTodayYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.2/5.0
Behavior5/5

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

Goes well beyond the readOnly/idempotent annotations: document links expire after an hour so re-list for fresh URLs, jobDescription is deliberately null to keep payloads small, moving a card never contacts the company, and the 24-hour rolling window that governs autoApplyRunsLeftToday. It also explains what applicationState and pendingQuestions mean, and discloses that inputs and results are privately recorded.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The opening sentence is well front-loaded, but the definition sprawls across four paragraphs with long enumerations of summary counters and state values that belong in the output schema. Useful content is present, yet several clauses (privacy notice, summary enumeration) are padding for a list tool.

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?

Rich enough for an agent to call correctly: paging via cursor, stage filtering, link expiry, and where to go for full records are all covered. Some field-level details duplicate the output schema, but nothing an agent needs is missing.

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

Parameters3/5

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

Only two parameters, both with 100% schema description coverage, so the schema already carries the semantics. The description repeats the stage values inside a parenthetical but adds no syntax or behavior for cursor/paging beyond the schema text; baseline 3 applies.

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 plus scope ('jobs the candidate applied to or plans to apply to'), and distinguishes itself from readApplication (single record with job description) and listMyPipeline (intros). The stage enumeration and ordering ('newest first') further pin down what comes back.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete routing: use readApplication when the full jobDescription is needed, use listMyPipeline for Clera intros, and call applyToJob with applicationId plus answers to recover an application whose runId was lost. It lacks an explicit 'don't use this when…' exclusion, but the alternatives are named and actionable.

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