Skip to main content
Glama

Worklittle Jobs

Jobs · List Applications

list_applications
Read-onlyIdempotent

Jobs — List the user's applications, newest first: ones Worklittle is filling out now (status active, with session_id to check or stop), pending ones (matched by auto-apply or waiting for approval) and finished ones (completed = submitted, failed, stopped). Use days for a period (7 = the last week). Check it before applying so the same job is never applied to twice. Filter with status, days, job_id or applicant_id. total counts every match; when next_offset is set, call again with that offset for the rest.

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

Input Schema

NameRequiredDescriptionDefault
daysNoOnly applications started or updated in the last this many days (7 = last week, 30 = last month).
limitNoMax rows to return (default 50, max 200).
job_idNo
offsetNoRows to skip: pass next_offset from the previous call to get the next page.
statusNo
applicant_idNo"me" for the user's own, or an applicant id (required on a shared API key)

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / limit / description
      Added value: +"Max rows to return (default 50, max 200)."
    • addedInput schema / properties / offset
      Added value: +{
      +  "description": "Rows to skip: pass next_offset from the previous call to get the next page.",
      +  "type": "number"
      +}
  2. Changed2 schema fields changed
    • addedInput schema / properties / days
      Added value: +{
      +  "description": "Only applications started or updated in the last this many days (7 = last week, 30 = last month).",
      +  "type": "number"
      +}
    • changedInput schema / properties / status / enum
      Previous value: -[
      -  "all",
      -  "pending",
      -  "matched",
      -  "awaiting_approval",
      -  "queued",
      -  "running",
      -  "awaiting_input",
      -  "awaiting_submit",
      -  "paused",
      -  "completed",
      -  "failed",
      -  "stopped"
      -]New value: +[
      +  "all",
      +  "active",
      +  "pending",
      +  "matched",
      +  "awaiting_approval",
      +  "queued",
      +  "running",
      +  "awaiting_input",
      +  "awaiting_submit",
      +  "paused",
      +  "completed",
      +  "failed",
      +  "stopped"
      +]
  3. Changed1 schema field changed
    • changedInput schema / properties / applicant_id / description
      Previous value: -"\"me\" for the user's own, or an applicant id"New value: +"\"me\" for the user's own, or an applicant id (required on a shared API key)"
  4. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the description's job is to add retrieval behavior — and it does: pagination is spelled out ('total counts every match; when next_offset is set, call again with that offset') and the status taxonomy is mapped to real lifecycle states. It doesn't cover ordering limits or what an empty result means, keeping it short of a 5.

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?

Front-loads purpose, then usage rule, then filters, then pagination — a sensible information hierarchy with no filler sentences. The status-parenthetical sentence is dense and slightly run-on, which costs a point.

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?

For a six-parameter, paginated list tool with an existing output schema, the description supplies what the schema cannot: lifecycle status meaning, pagination protocol, and the pre-apply check workflow. Only the semantics of job_id and applicant_id scoping are left implicit (partially in schema), so it is nearly complete.

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?

At 67% schema coverage the description must add meaning, and it does for days ('7 = the last week'), for status (grouping enum values into active/pending/finished), and for pagination via next_offset. job_id and limit are left entirely to the schema, so it doesn't fully compensate for the coverage gap.

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+resource ('List the user's applications, newest first') and immediately decomposes the result into meaningful buckets: active (with session_id to check or stop), pending (auto-apply or awaiting approval), and finished (completed/failed/stopped). An agent can tell this apart from check_application_status or search_jobs without opening the schema.

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 a concrete workflow rule ('Check it before applying so the same job is never applied to twice') plus how to use days and which filters exist. It stops short of explicitly naming alternatives ('use check_application_status for a single job'), so context is clear but without explicit exclusions.

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