get_jobGet the full details of a single published job by its advertising UID.
| Name | Required | Description | Default |
|---|---|---|---|
| uid | Yes | Advertising UUID of the job (accepts full or shortened form) |
| Name | Required | Description | Default |
|---|---|---|---|
| uid | Yes | ||
| title | Yes | ||
| company | No | ||
| applyUrl | No | ||
| benefits | No | ||
| location | No | ||
| workplace | No | ||
| department | No | ||
| description | No | ||
| requirements | No | ||
| employmentType | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds the useful context that only published jobs are accessible and that it returns full details, but it does not disclose additional behavioral traits such as error behavior or unpublish edge cases. This is adequate but not rich.
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 sentence that is entirely relevant and clearly structured. It states the action, the target resource, the scope, and the required identifier without any filler, making it easy for an agent to parse quickly.
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?
The tool has one documented parameter, a read-only annotation set, and an output schema. The description supplies the remaining needed context: it fetches full details of a single published job by UID. Nothing essential is missing for correct invocation.
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 input schema has 100% coverage for the single parameter, uid, including its type and accepting full or shortened forms. The description essentially restates the parameter's purpose without adding material new meaning, so the baseline score of 3 applies.
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 specifies a precise verb and resource: getting the full details of a single job by its advertising UID. It clearly distinguishes this from sibling tools like search_jobs or get_company by focusing on a single job and a unique identifier.
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 clearly implies when to use the tool: when you have a job's advertising UID and need full details for that specific job. It does not explicitly mention when not to use it or name alternatives, but the context is clear enough for an agent to select it correctly.
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.