Skip to main content
Glama

Worklittle Jobs

Jobs · Add Applied Job

add_applied_job
DestructiveIdempotent

Jobs — Add a job to the user's applied jobs (Applied and Saved on worklittle.com) at a status such as saved or applied. To move a job already there, use update_applied_job.

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": {
      "job_id": "<job_id>",
      "job_title": "<job_title>",
      "company_name": "<company_name>"
    },
    "name": "add_applied_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYesWorklittle job id from search_jobs or get_job_details.
methodNoHow the user applied. Defaults to apply.
statusNoPipeline stage when known. Use saved for heart/save. Defaults to in_progress for apply / apply_with_ai, applied for api.
apply_urlNoOptional employer apply URL.
job_titleYes
company_nameYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, idempotentHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful context that the write is to the user's site-side Applied/Saved collections and that the status can be a pipeline stage, but it does not address idempotency behavior on a duplicate job_id, what gets overwritten, or auth requirements — the things an agent would actually want to know before writing.

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 sentences, zero filler. The primary action is front-loaded and the sibling redirect follows in second position.

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 an output schema present, the description needn't explain return values, and the annotations plus the sibling redirect cover the main gaps for a 6-parameter mutation. The residual gap is duplicate-handling and field-overwrite semantics, which matter given idempotentHint=true and a destructiveHint=true annotation on an 'add' operation.

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 67% and the schema descriptions for job_id, method, status and apply_url are already detailed, including enum defaults. The description only echoes status values ('saved or applied') that the schema states more completely, and says nothing about the two undocumented fields (job_title, company_name) or whether they are overwritten on an existing entry. Baseline 3 is appropriate.

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 ('Add a job to the user's applied jobs'), names the destination (Applied and Saved on worklittle.com), and disambiguates from the near-identically named sibling by pointing at update_applied_job for jobs already present. An agent can tell what it does and what it is not 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 Guidelines5/5

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

Gives both sides of the routing decision: use this for a job not yet in the user's list, use update_applied_job to move a job that is already there. That is an explicit alternative plus the condition that selects it.

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