Skip to main content
Glama

Jobiba Hiring: Post Jobs, Screen Applicants & Source Talent

Review a job post

review_job_post
Read-onlyIdempotent

Scores a job post (an existing jobId or a draft title and description) on length, structure, salary transparency, skills, inclusive language and clarity, and compares stated pay with published market salaries.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "review_job_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobIdNoJobiba job ID (the id field from search_jobs or list_my_jobs).
titleNoDraft title.
skillsNo
locationNoDraft location.
salaryMaxNoDraft maximum pay.
salaryMinNoDraft minimum pay.
descriptionNoDraft description.
salaryCurrencyNoCurrency.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and closed-world scope, so the safety profile is covered. The description adds real behavioral value beyond that: it discloses that the tool both scores on named rubrics and performs an external market-salary comparison of stated pay, which is a non-obvious side effect. It does not, however, say what happens if both jobId and draft fields are supplied.

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 front-loaded sentence that leads with the verb and parenthetical input modes before listing rubrics. Every clause carries information and there is no filler, though the rubric list makes the sentence long enough that it is slightly dense for a single read.

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 8 optional parameters and no output schema, the description does well to imply the return dimensions by enumerating what is scored. It is still incomplete on two points an agent would want: which combinations of jobId versus draft fields are valid, and whether the market-salary comparison requires salaryMin/salaryMax to be present.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is already 88%, so the schema documents most fields. The description still adds meaning the schema cannot express: the two mutually exclusive input shapes (jobId for an existing post, title/description/salary fields for a draft). With zero required parameters, that dual-mode framing is the key semantic an agent needs and it is supplied here.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (scores) and resource (a job post), then enumerates the exact dimensions evaluated (length, structure, salary transparency, skills, inclusive language, clarity) plus a market-pay comparison. It also names the two input modes — existing jobId or draft title/description — which separates it cleanly from siblings like post_job, draft_job_post and salary_analysis.

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?

The parenthetical implies two usage modes (review a live posting vs. a pre-publish draft), which is useful context. However, it never states when to prefer this over salary_analysis or salary_calculator for the pay dimension, nor any preconditions such as needing an existing job to have a jobId first. Usage is implied rather than directed.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.