get_recent_searchesList popular/recent job search terms, tailored to your last known location, with a URL to run each search.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| searches | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already cover readOnlyHint=true and destructiveHint=false, so the description does not need to restate safety. It adds useful behavior beyond annotations: results are 'tailored to your last known location' and each item includes 'a URL to run each search.' These are concrete behavioral traits not available from structured fields.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single, front-loaded sentence that states the core action first and then adds two relevant qualifiers. Every phrase earns its place and there is no filler.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a zero-parameter, read-only tool with an output schema present, the description is complete. It explains what will be returned conceptually, mentions the location context, and notes the actionable URL, leaving no material gap for an agent to call it correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters and schema coverage is 100%, so there is nothing for the description to clarify. The baseline for no-parameter tools is 4, and the description appropriately focuses on behavior rather than inventing parameter information.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description opens with 'List popular/recent job search terms', which states a specific verb and resource. It adds meaningful detail—location tailoring and a URL for each search—that clearly separates it from siblings like search_jobs or get_recommendations.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies a use case—when you want popular or recent search terms—but it never explicitly tells the agent when to choose this tool over alternatives. It does not mention sibling tools like search_jobs or provide when-not-to-use guidance, so the agent must infer the boundary.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct resource and action, with clear boundaries between search, recommendations, and recent searches. The descriptions resolve any potential overlap, making misselection unlikely.
All tool names follow a consistent action_noun pattern in snake_case. Get operations use 'get_', while update, withdraw, and search operations use their respective verbs, maintaining a predictable convention.
With 10 tools, the server is well-scoped for its purpose, covering job search, application management, and profile handling without unnecessary bloat or a thin surface.
The toolset covers job search, job details, profile retrieval/update, and application withdrawal. However, there is no direct 'apply' tool, which is a notable gap in a job-focused server, though agents can work around it via external links.