Skip to main content
Glama

jobctl

by io.github.DmytroRybka

List applications

list_applications
Read-only

List job applications. Filter by view (active = default working set, archive = rejected/withdrawn/no-response), status list, priority, or free-text search in company/role. Example: list_applications({view: "active"}), list_applications({q: "bosch"}).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoSearch in company/role
viewNo
limitNo
statusNoComma-separated: started_apply, waiting_referral, applied, waiting, interview, offer, accepted, rejected, no_response, on_hold, withdrawn, archived
priorityNo

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already indicate readOnlyHint=true. Description adds context about filter capabilities and view semantics, beyond what annotations provide. No contradictions.

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

Conciseness5/5

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

Two concise sentences plus example. Front-loaded with purpose, then filters. Every sentence provides value without redundancy.

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?

With 5 parameters and no output schema, description covers the main filtering aspects. Missing pagination/limit details, but acceptable for a list tool. No return format but not required.

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 40%, but description compensates by detailing view values, search field (q), status list, and priority. Missing explanation for limit, but overall adds significant meaning beyond the schema.

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?

Clearly states 'List job applications' with specific verb and resource. Distinguishes from siblings like get_application (single retrieval) and add_application (creation) by focusing on listing and filtering.

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?

Examples show typical usage patterns (e.g., filtering by view, searching). Explains view meanings ('active = default working set, archive = rejected/withdrawn/no-response'). Could explicitly state when to use alternatives like get_application, but overall clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All jobctl toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation5/5

Every tool targets a distinct resource and action: application, note, analysis attachment, file attachment, interview file, application detail, due actions, planned schedule, application listing, interview logging, and application updates. Even the three 'attach' tools are clearly differentiated by purpose (analysis vs CV/cover letter vs interview prep). The only potential overlap between get_due and get_planned is explicitly resolved in the descriptions.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern in snake_case (add_application, get_application, list_applications, update_application, attach_analysis, log_interview, etc.). The verb prefix accurately reflects the action, and nouns are singular for single-item operations and plural for list operations, maintaining a predictable convention.

Tool Count5/5

With 11 tools, the server is well-scoped for a job application tracking domain. Each tool covers a necessary function without redundancy, and the count is neither sparse nor overwhelming.

Completeness4/5

The tool set covers the full lifecycle of an application: create, read, list, update, plus notes, attachments, analysis, and interview logging. Minor gaps exist—there is no explicit delete or archive tool (though status updates can archive), and interviews cannot be directly updated or removed after logging—but these are workable within the existing surface.

Resources