Skip to main content
Glama

Campus Jobs Radar 校招雷达

Search Jobs

search_jobs

按条件搜索国央企校招岗位/招聘项目。

参数: city: 工作地点关键词(如 "深圳"、"广东";为空查全部)。"雄安"会自动带上容城/安新/雄县。 major: 专业关键词。先匹配"专业要求原文"(major_raw);原文缺失时在公告正文里找, 所以能覆盖那些只有公告、没拆出专业字段的岗位(如 "计算机"、"会计") graduate_year: 届别,如 "2027"。严格匹配公告标注的届别——未标注届别的记录不会被返回; 想广撒网就别传这个参数。 keywords: 对岗位名/单位名做包含匹配 kind: "岗位" | "招聘项目" | "宣讲会"(为空查前两类) org_nature: 企业性质筛选。默认 "国央企"(=央国企+地方国企+银行); 传 "全部" 看所有(含顺带覆盖的民企/事业单位/未知长尾); 也可精确传:央国企/地方国企/银行/事业单位/民企/外企/未知 employment_type: 批次筛选:"校招" | "实习" | "提前批"(为空查全部) only_open: 只返回未截止的(默认 True,按北京日期判断) limit/offset: 分页(默认每页 20,上限 50)

返回字段含截止日、剩余天数、截止状态、专业要求原文、企业性质、原公告链接、数据复核日期。 未写明的条件留空(null),本服务不猜测;重大决策请打开 source_url 核对原文。

Input Schema

NameRequiredDescriptionDefault
cityNo
kindNo
limitNo
majorNo
offsetNo
keywordsNo
only_openNo
org_natureNo国央企
graduate_yearNo
employment_typeNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / employment_type
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null
      +}
  2. Changed1 schema field changed
    • addedInput schema / properties / org_nature
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": "国央企"
      +}
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

无注解,描述补充了重要行为:only_open 默认 True 按北京日期判断、graduate_year 严格匹配且未标注届别不返回、kind 为空查前两类、org_nature 默认国央企及全部含义、分页上限 50。还说明了返回字段(截止日、剩余天数、来源链接等),透明度较高,但未提及速率限制或权限需求。

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?

采用参数列表结构清晰,关键约束(默认值、枚举)前置。内容较长但每句都有实质信息,无明显冗余。

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

有输出 schema 但描述仍概括了返回字段(截止日、剩余天数、状态、专业原文、企业性质、公告链接、复核日期),并提示未明字段为 null、需核对原文。对于搜索类工具,参数行为、返回概览、决策提示均已覆盖,完整度高。

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

schema 描述覆盖率为 0%,描述对全部 10 个参数逐一解释,包括枚举取值、默认值、特殊逻辑(如“雄安”自动带容城/安新/雄县、major 匹配原文与公告正文、graduate_year 严格匹配)。补偿充分,远超 schema 提供的信息。

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?

明确说明了动词(搜索)和资源(国央企校招岗位/招聘项目),并限定了目标人群范围。与 get_job_detail(详情)、list_deadlines(截止日)、whats_new(新品)等兄弟工具区分明显,但未直接点名替代工具。

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?

对关键参数给出了使用建议(如只查未截止的用 only_open,想广撒网不传 graduate_year),并提示重大决策需核对原文。但未明确说明何时应改用 get_job_detail 或 list_deadlines 等兄弟工具。

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.