Skip to main content
Glama

search_campus_jobs

Read-only

在面灵AI 的校招 / 实习岗位库中搜索在招岗位,返回第一页结果(每行一个岗位)。投递直达链接与后续翻页需在面灵AI 网站登录后查看。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_campus_jobs"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNo工作城市,如「上海」,取值见 get_campus_job_filters 的 city 一行
sortNohot = 热度,recent = 最近收录,published = 最近发布hot
companyNo公司名,如「字节跳动」
keywordNo岗位名称或职责关键词,如「后端开发」「产品经理」
jobFunctionNo职能,取值见 get_campus_job_filters 的 jobFunction 各行
employmentTypeNo招聘类型,取值见 get_campus_job_filters 的 employmentType 一行

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 already cover safety (readOnlyHint=true, destructiveHint=false, openWorldHint=false), so the description's added value is what really counts. It discloses result shape (one job per line), the first-page-only cap, and the login gate for direct application links and further pages — concrete operational limits an agent would otherwise discover only by failing.

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?

Two sentences: the first front-loads the search action and result scope, the second front-loads the access limitation. No filler and nothing repeated from structured fields beyond what is necessary.

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?

With no output schema, the description must characterize returns, and it does (first page, one job per line) while flagging the login-gated follow-up. Six optional filters are fully documented in the schema, so nothing critical is missing; only a clearer statement of default behavior or result-volume expectation is absent.

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 description coverage is 100%: every one of the six parameters carries an example and, for city/jobFunction/employmentType, a pointer to get_campus_job_filters for valid values. The description adds nothing beyond the schema, which is the correct baseline case.

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 (搜索/search) and a clearly bounded resource (在招岗位 in the 校招/实习 job library), so an agent knows exactly what comes back. It does not name any sibling tool, so differentiation (e.g. versus get_campus_job_filters) is left to inference.

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 implied by the scope statement: search this library for open roles. It also usefully states that only the first page is returned and that pagination/application links require website login, which implicitly tells the agent not to attempt paging here. However, there is no explicit when-to-use/when-not-to-use rule or named alternative.

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