Skip to main content
Glama

add_campus_job_to_apply_list

Add a job from the job library to the user's Auto Apply list, optionally choosing the resume for it (the base resume otherwise). Jobs already on the list are not added twice. Replies with the application as read back, including its id. (Requires the user's sign-in with scope job_applications:write.)

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": {
      "campusJobId": "<campusJobId>"
    },
    "name": "add_campus_job_to_apply_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
resumeIdNoResume id, from list_resumes
campusJobIdYesJob id, from search_campus_jobs

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing idempotency ('Jobs already on the list are not added twice'), the resume default fallback to the base resume, the auth prerequisite with the required scope (job_applications:write), and what the response contains. With readOnlyHint=false and destructiveHint=false already given, this adds real behavioral context an agent needs before calling.

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?

Three compact sentences, each carrying distinct information: action, idempotency, return value, and auth. No filler, and the primary action is front-loaded.

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 two-parameter mutation with no output schema, the description covers the action, the optional-parameter default, duplicate handling, the returned application id, and the auth requirement. Nothing essential to correct invocation is missing.

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 100%, so the baseline is 3, but the description adds meaning the schema does not: resumeId is optional and defaults to the base resume. It also clarifies campusJobId comes from the job library, though it stops short of naming search_campus_jobs as the source.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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 from the job library to the user's Auto Apply list') with scope detail about the optional resume. The 'from the job library' phrasing implicitly separates it from the link- and manual-job siblings, but no sibling is named explicitly.

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

Usage Guidelines3/5

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

Usage is implied by the resource ('Auto Apply list') and the idempotency note tells the agent duplicate calls are harmless, but there is no explicit when-to-use/when-not guidance or reference to add_job_link_to_apply_list and add_manual_job_to_apply_list for other job sources.

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