Skip to main content
Glama

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

Input Schema

NameRequiredDescriptionDefault
resumeIdNo简历 ID,从 list_resumes 取得
campusJobIdYes岗位 ID,从 search_campus_jobs 取得

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

The annotations only state that this is a non-read-only, non-destructive, closed-world operation. The description adds real behavioral context beyond them: adding a job that already exists is idempotent (no duplicate), the resume falls back to the base resume when resumeId is omitted, the write requires the job_applications:write scope, and the response is the re-read application record with its ID.

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 is front-loaded, and each following clause adds a distinct fact (resume override, idempotency, return payload, auth scope) with no filler. The single dense paragraph is efficient, though splitting the auth/return note into its own sentence would improve scannability.

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 tool with no output schema, the description covers what is written, the default for the optional parameter, the duplicate-handling rule, the return shape, and the authorization requirement. The only gap relative to its siblings is that it does not explicitly say which tool to use for manual or link-based jobs.

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?

With 100% schema description coverage, the baseline is 3, and the description earns a bump by explaining resumeId's default behavior (base resume if unspecified), which the schema does not state. That default is exactly the kind of meaning that schema cannot convey.

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 from the job library (岗位库中的一个岗位) into the user's application submission list. The phrase 'from the job library' implicitly distinguishes it from the manual/link-based siblings, but it never names those siblings, so an agent must infer the distinction rather than read it.

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 only implied by the purpose statement; there is no explicit guidance on when to pick this over add_manual_job_to_apply_list or add_job_link_to_apply_list, nor any prerequisite flow beyond the parameter hints. The authorization scope note helps confirm the required setup but does not route between alternatives.

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