Skip to main content
Glama

校招宝 · 中国校园招聘岗位数据

岗位详情(含 JD)

get_job_detail
Read-only

按岗位 ID 获取单条校招岗位的完整信息与 JD 全文。当需要判断匹配度、对比两个岗位、回答该岗位的具体要求时使用。ID 取自 search_campus_jobs 的返回结果。

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": {
      "id": "<id>"
    },
    "name": "get_job_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes岗位 ID(来自 search_campus_jobs 的 id 字段)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds that the payload includes full JD text (完整信息与 JD 全文), but with no output schema it remains vague about what '完整信息' actually contains and does not mention failure behavior for an invalid ID.

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: what it returns, when to use it, and where the key comes from. The purpose and the constraint are front-loaded with no filler.

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 one-parameter read tool with safety annotations and no output schema, the description covers retrieval scope, key sourcing, and the JD payload adequately. Only a brief note on what the returned 'complete info' includes would make it fully self-sufficient.

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?

There is a single parameter with 100% schema description coverage, so the schema already documents the id field and its provenance. The description only repeats that the ID comes from search_campus_jobs, adding no format or validity detail beyond the structured field.

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 (获取) plus resource (单条校招岗位的完整信息与 JD 全文) and scope (单条, keyed by 岗位 ID). It also names the sibling that produces the ID (search_campus_jobs), so an agent can distinguish it from the search tool without inspecting schemas.

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 concrete usage contexts: judging match quality, comparing two positions, answering a position's specific requirements, and where the ID comes from. There is no explicit 'when not to use' or statement that bulk retrieval should go through search_campus_jobs, so it stops short of a full routing rule.

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.