Skip to main content
Glama

Jobiba Hiring: Post Jobs, Screen Applicants & Source Talent

My job posts

list_my_jobs
Read-onlyIdempotent

The employer's jobs with open/closed state, applicant counts, impressions and clicks.

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": "list_my_jobs"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax 50.
offsetNoPaging offset.
statusNoFilter.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety and side-effect behavior are covered. The description's real contribution is disclosing the payload fields (applicant counts, impressions, clicks) in the absence of an output schema, but it says nothing about pagination behavior, ordering, or total counts for paged reads.

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 well-formed sentence with zero filler, and the resource plus returned fields are front-loaded. It is efficient, though the terseness is achieved partly by omitting genuinely useful information rather than by tight editing.

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 only three optional, fully documented parameters and no output schema, the description does cover the salient return fields. What is missing is the scope statement (own jobs only) and any usage routing, which for a tool sitting among search_jobs, get_job and employer_dashboard leaves a meaningful gap.

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

Parameters3/5

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

Schema description coverage is 100%, so limit, offset and status are already documented in the schema, establishing the baseline of 3. The description's mention of 'open/closed state' loosely echoes the status enum but adds no filtering semantics, defaults, or paging guidance beyond what the schema supplies.

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

Purpose3/5

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

The description names the resource ('The employer's jobs') and enumerates the returned data (state, applicant counts, impressions, clicks), which hints at a listing of the caller's own job posts and distinguishes it from search_jobs. However, it is a bare noun phrase with no verb, so the agent must infer that this is a paged list operation rather than a detail fetch like get_job.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance at all: nothing tells the agent to prefer this over search_jobs, get_job, or employer_dashboard, and nothing states the implicit scope constraint (only the caller's own jobs). The agent has to derive usage from the sibling names alone.

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.