Retrieve one Meta Careers job posting using its numeric job ID from search or list results, returning structured JSON with role details.
Meta Jobs single posting. Returns one Meta Careers posting by its numeric job id (the id field returned by search or list).
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Meta job id |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. Calling it a 'Returns' operation implies a read-only lookup, but it omits error behavior, rate limits, and what a posting record actually contains, leaving real gaps for the only source of behavioral context.
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?
Two tight sentences, front-loaded with the identifier and purpose, with the id-provenance note placed immediately after. Nothing is redundant or padded.
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 single-parameter read tool with a rich schema, the description covers the essential what and where-the-id-comes-from. It is nearly complete; the main omission is any hint about the returned posting's contents, which matters slightly since no output schema exists.
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?
Schema coverage is 100% and the schema already labels the field 'Meta job id', so the baseline is 3. The description adds real value by specifying the id is numeric and that it comes from the search or list tools, clarifying provenance and expected type beyond the schema.
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 states a specific verb and resource: returns one Meta Careers posting by numeric job id. The phrase 'single posting' plus the reference to results from 'search or list' implicitly separates it from meta_jobs_search and meta_jobs_list, though those siblings are not named directly.
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?
It tells the agent exactly when this tool applies: after obtaining an id from search or list. There is no explicit exclusion or failure guidance (e.g., invalid or missing id), but the retrieval context is clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.