get_postingFetch a single posting by its ID from search results to retrieve detailed listing data for AI clients.
Fetch one posting by the id returned from search.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | ||
| raw | No | ||
| url | No | ||
| title | Yes | ||
| company | No | ||
| currency | No | ||
| location | No | ||
| posted_at | No | ||
| salary_max | No | ||
| salary_min | No | ||
| description | No |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description adds only the provenance of the id value, not return format, error behavior, or missing-id handling.
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 tight sentence with the key constraint (one posting, by id from search) front-loaded and zero 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?
An output schema exists, so return values need not be explained. For a one-param lookup with full annotations, the description covers what an agent needs, though a note on missing ids or errors would complete it.
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 single parameter has 0% schema description coverage, so the description must carry the meaning. "id returned from search" usefully tells the agent where the id originates, but gives no format or validation details.
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?
States a specific verb (Fetch) and resource (one posting) with a clear singular scope. It implicitly distinguishes itself from the search sibling by noting the id comes from search, but never names the alternative explicitly.
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 id returned from search" implies this is a follow-up call to search, which is useful sequencing context. However, there is no explicit when-to-use/when-not guidance or named alternative to route the agent.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.