Skip to main content
Glama

Read one tracked job application

readApplication
Read-onlyIdempotent

Read one application on the candidate's job tracker by its applicationId, with everything listApplications shows plus the full job description (jobDescription, null when none was saved) and activity: what happened on it, newest first (stage moves, employer emails to their apply address with the email text, the message they sent the hiring team and its reply). Use it before tailoring advice, interview prep or editing the description with updateApplication. 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.

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": {
      "applicationId": "<applicationId>"
    },
    "name": "readApplication"
  }
}

Input Schema

NameRequiredDescriptionDefault
applicationIdYesThe id from a listApplications or trackApplication result.

Output Schema

NameRequiredDescriptionDefault
activityYes
applicationYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare a safe read (readOnly, idempotent, non-destructive, not open-world), and the description adds real behavior beyond that: jobDescription is null when none was saved, activity is ordered newest first and enumerates its contents (stage moves, employer emails with text, message and reply), plus a privacy note that inputs/results are recorded. The 'moving a card never contacts the company' line is slightly tangential to a read tool but reinforces the no-side-effect profile.

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?

The scope and purpose are front-loaded in the first clause, and the alternative-routing follows immediately. It runs long with some surplus material (the card-moving remark, the privacy boilerplate), but nothing is buried before the essential identification.

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 one-parameter read tool with full schema coverage and an output schema, everything needed is present: what it returns at a high level, null handling, ordering, sibling routing, and side-effect semantics. No gap remains that would cause a misinvocation.

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?

Schema coverage is 100% and the single parameter already documents that the id comes from listApplications or trackApplication results; the description only restates that the lookup is by applicationId. With the schema doing the heavy lifting, 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?

Specific verb+resource+key: reads a single application by applicationId, and explicitly delimits scope against siblings — 'everything listApplications shows plus' the job description and activity. It also distinguishes tracked jobs from Clera intros, naming listMyPipeline as the tool for those.

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 concrete when-to-use conditions ('before tailoring advice, interview prep or editing the description with updateApplication') and names the sibling to use for the case this tool doesn't cover (listMyPipeline for intros). Exclusions and alternatives are both present.

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