Skip to main content
Glama

discover_jobs

Read public career sites for a saved job goal and return real job-description candidates, source-read results, and items to verify; skips dynamic or login-only sites and never invents contact emails.

Instructions

按已保存目标读取公开官网,返回真实 JD 候选、来源读取结果和待核对信息;不承诺覆盖动态或登录网站,不编造邮箱。

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": {
      "goalId": "<goalId>"
    },
    "name": "discover_jobs"
  }
}

Input Schema

NameRequiredDescriptionDefault
goalIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations (readOnlyHint=false, openWorldHint=true, destructiveHint=false) cover the safety profile, and the description adds real context: the tool reads external live sites, returns source-read results and items needing verification, and explicitly disclaims coverage of dynamic/login-gated pages and fabricated emails. It does not clarify whether discovered candidates are persisted, which matters given readOnlyHint=false.

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?

A single compact sentence, verb-first, with the caveats front-loaded after the return-value clause. Dense but every clause carries information; the semicolon structure is readable.

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

Completeness3/5

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

With one required parameter and no output schema, the description does a fair job naming the return components and the tool's limits. It still leaves open how goalId is sourced and whether results persist, which an agent needs before invoking a non-read-only, open-world tool.

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?

Only one parameter (goalId) at 0% schema description coverage. The description's '按已保存目标' is the only signal that goalId refers to a previously saved search goal rather than an arbitrary string, but it does not state the format or how to obtain a valid goalId.

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?

A concrete verb (读取) plus resource (公开官网 / public official sites) and a stated output type (真实 JD 候选, 来源读取结果, 待核对信息). An agent can tell this apart from add_job or goal_candidates, though no sibling is named explicitly.

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?

Implies the precondition that a saved goal must exist ('按已保存目标') and states limits (no dynamic or login-required sites), which is useful. But it never says when to prefer this over goal_candidates or save_search_goal, leaving the routing decision to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.