Skip to main content
Glama

add_job_link_to_apply_list

Add a job to the user's Auto Apply list by its application link (careers sites, referrals, shared links). Links in the job library map to that job; others are shown by domain until the company and title are identified in the background. Optionally choose the resume. 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": {
      "url": "<url>"
    },
    "name": "add_job_link_to_apply_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe application link
resumeIdNoResume id, from list_resumes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior2/5

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

Annotations declare readOnlyHint=false, so the agent knows this is a write. The description does mention the write scope and that some links resolve in the background, but it omits the critical side effect: adding a link actually triggers an automated job submission. That omission is materially misleading about what the operation does.

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?

Four sentences, each carrying information: purpose, link resolution behavior, the resume option, and the auth scope. Front-loaded with the action, though the parenthetical link examples and the nested background-resolution clause make it denser than necessary.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description does well to say it replies with the application as read back including its id. It covers auth and async resolution, but as a mutation tool with no annotations clarifying side effects, it leaves the agent without a clear picture of what the add actually initiates.

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%, so both parameters are already documented, and the description adds only that the link may come from careers sites, referrals, or shared links. That broadens understanding of accepted URL forms beyond the schema's 'The application link', but resumeId gets no added meaning beyond the schema's reference to list_resumes.

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 to the user's Auto Apply list') plus the distinguishing mechanism ('by its application link') with examples of link types (careers sites, referrals, shared links). It implicitly separates itself from the manual and campus variants, though it never names them.

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 input shape: use this when you have a URL rather than a manual entry or campus posting. However, it never explicitly says when to prefer it over add_manual_job_to_apply_list or add_campus_job_to_apply_list, and gives no prerequisites beyond the auth scope.

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