Skip to main content
Glama
Sign In

Jobiba Hiring: Post Jobs, Screen Applicants & Source Talent

by com.jobiba
OverviewDiscussionsAdmin

Shortlist or skip a candidate

shortlist_candidate
Destructive

Shortlist (bookmark) or skip a candidate from talent search; this also trains your future match ranking.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "candidateProfileId": "<candidateProfileId>",
      "action": "<action>"
    },
    "name": "shortlist_candidate"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobIdNoJob context.
actionYesWhat to do.
candidateProfileIdYescandidateProfileId.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

The annotations already declare this as a non-read-only, non-idempotent, potentially destructive write. The description adds genuinely new behavioral context beyond that: the action 'trains your future match ranking,' which is a non-obvious side effect an agent could not infer from annotations or schema. It does not, however, explain what 'destructive' means here or whether shortlist/skip can be reversed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with the primary action first and a second clause for the side effect; the parenthetical '(bookmark)' clarifies the synonym without padding. Every clause earns its place.

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?

For a small three-parameter mutation with full schema coverage and annotations, the description covers purpose and the ranking side effect adequately. It leaves gaps around reversibility of skip, the optional jobId's effect on behavior, and confirmation of what state changes occur — meaningful for a tool flagged destructive and non-idempotent.

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% and the enum on action is self-documenting, so the schema carries parameter meaning. The description adds nothing about jobId's role as optional context versus required, or what happens when jobId is omitted — baseline 3 applies.

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

Purpose4/5

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

Names specific verbs (shortlist/bookmark, skip) against a clear resource (candidate) and scopes it to talent search, so an agent can distinguish it from list_shortlist. It stops short of explicitly contrasting itself with the sibling that reads the shortlist, but the action is unambiguous.

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 phrase 'from talent search' implies the tool is used after a search result is in hand, which is useful context. There is no explicit when-not guidance, no mention of how to undo a shortlist or skip, and no reference to alternatives such as list_shortlist to verify state.

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

All Jobiba Hiring: Post Jobs, Screen Applicants & Source Talent toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources