Skip to main content
Glama

add_job_link_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": {
      "url": "<url>"
    },
    "name": "add_job_link_to_apply_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes岗位的投递链接
resumeIdNo简历 ID,从 list_resumes 取得

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare it is a non-read-only but non-destructive, closed-world write. The description adds genuinely useful behavior beyond that: unmatched jobs first create a domain-based placeholder with background company/title resolution, the response returns the read-back record and its ID, and it discloses the required authorization scope job_applications:write. It does not address duplicate handling or failure behavior, keeping it below 5.

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?

The purpose and accepted link forms are front-loaded, followed by resolution behavior, resume option, response, and auth scope in a compact sequence. It is dense with parenthetical asides but every clause carries actionable information; only the parenthetical auth note could be tightened.

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 two-parameter write with no output schema, the description covers what it does, what happens to unknown jobs, the optional resume, the returned record and ID, and the auth requirement. Only edge cases such as re-adding an already-listed job are unaddressed.

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 url and resumeId are already documented, including the pointer to list_resumes. The description only restates that a resume can additionally be specified, adding no format, constraint, or fallback semantics beyond the schema.

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?

The description states a specific verb and resource ('add a job to the user's application list by submission link') and narrows the input form to a URL, which separates it from the link-less variants such as add_manual_job_to_apply_list and add_campus_job_to_apply_list. It also enumerates acceptable link sources (official site, referral, forwarded), so the agent knows exactly what kind of input qualifies.

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?

Acceptable link types are spelled out, which gives implied usage context (any external job link can be added here). However, the description never explicitly contrasts this with the sibling adders or states when-not to use it, leaving the routing decision to be inferred from tool names alone.

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