Skip to main content
Glama

add_manual_job_to_apply_list

Add a job that is not in the job library to the user's Auto Apply list by entering the company and title. One record per company and title. 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": {
      "company": "<company>",
      "jobTitle": "<jobTitle>"
    },
    "name": "add_manual_job_to_apply_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
citiesNoWork locations (optional)
jobUrlNoJob link (optional)
companyYesCompany name
jobTitleYesJob title

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the annotations (which only say it is a non-read-only, non-destructive, closed-world write), the description discloses the auth requirement and scope ('sign-in with scope job_applications:write'), a dedup rule ('one record per company and title'), and the response shape ('replies with the application as read back, including its id'). That is meaningful behavioral context the annotations do not carry.

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 short sentences, front-loaded with the action and scope, then the uniqueness rule, then the return and auth note. No filler or restatement of the tool name.

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 no output schema, the description usefully states what comes back (the application record with its id), and it covers auth and duplicate handling for a write tool. The optional parameters are left entirely to the schema, which is acceptable given full coverage but is a small remaining gap.

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 description coverage is 100%, so the schema already documents all four parameters including the optional cities and jobUrl. The description only restates the two required fields and ties them to the dedup rule; it adds no format or constraint detail beyond the schema, so the baseline 3 applies.

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?

The description gives a specific verb and resource ('Add a job ... to the user's Auto Apply list') plus the method ('by entering the company and title') and a scope condition ('not in the job library'). That implicitly separates it from library-based and URL-based siblings, 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 Guidelines4/5

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

The clause 'a job that is not in the job library' is a genuine when-to-use condition, and 'by entering the company and title' tells the agent what input path this tool represents. It stops short of naming the alternative tools (e.g. the job-link or campus variants) or stating exclusions explicitly.

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