Skip to main content
Glama

add_manual_job_to_apply_list

手动填写公司与岗位,把岗位库未收录的岗位加入用户的网申投递清单。同一公司同一岗位名只保留一条。回包为读回的投递记录与 ID。(需要用户授权,范围 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
citiesNo工作城市(选填)
jobUrlNo岗位链接(选填)
companyYes公司名
jobTitleYes岗位名

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare a non-destructive write with no open-world access, and the description adds genuine value on top: the dedupe rule (one record per company+job title), the response shape (read-back record plus ID), and the required authorization scope job_applications:write. Only the conflict behavior (update vs. no-op on duplicates) is left ambiguous.

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 short sentences, front-loaded with the action and target, then the dedupe rule, then the response, then the auth scope. No filler; each sentence carries a distinct fact.

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 four-parameter write tool with no output schema, the description covers purpose, dedupe semantics, return value, and authorization scope. What remains unstated is only edge behavior on duplicate submission, which is minor relative to what is disclosed.

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 description coverage is 100%, so per-field meaning is already documented; the description adds the semantic that company plus jobTitle together form the dedupe key, which is meaning beyond the schema. It says nothing extra about cities or jobUrl, but the schema covers them adequately.

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 states a specific verb and resource: manually enter company and job title to add a posting not covered by the job library into the user's application list. The 'not in the job library' qualifier implicitly separates it from link-based or campus variants, though 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 Guidelines4/5

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

It gives a clear selection condition (use this when the job is not in the library and must be entered manually), which is what an agent needs to pick between manual entry and link/campus entry. It stops short of naming those alternatives or stating 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