Skip to main content
Glama
Sign In

Jobiba Hiring: Post Jobs, Screen Applicants & Source Talent

by com.jobiba
OverviewDiscussionsAdmin

Message a candidate

message_candidate
Destructive

Sends recruiter outreach to a talent-search candidate. Without confirm=true it returns a preview and sends nothing; with confirm=true it sends an email through Jobiba (limits: 20 per day, 2 per candidate per 30 days). The candidate's contact details are never exposed.

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": {
      "jobId": "<jobId>",
      "candidateProfileId": "<candidateProfileId>",
      "subject": "<subject>",
      "message": "<message>"
    },
    "name": "message_candidate"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobIdYesJobiba job ID (the id field from search_jobs or list_my_jobs).
confirmNotrue only after explicit user approval.
messageYesMessage (20+ chars). Be specific and honest about the role.
subjectYesEmail subject (4+ chars).
candidateProfileIdYescandidateProfileId from find_candidates.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Goes well beyond the annotations (destructive/openWorld/non-idempotent) by disclosing the dry-run default, the delivery channel (email via Jobiba), concrete quotas (20/day, 2 per candidate per 30 days), and a privacy guarantee that contact details are never exposed. These are exactly the side effects and constraints an agent needs before invoking a destructive outbound action, and they are consistent with the annotations.

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?

Three dense sentences, front-loaded with the action, then the confirm gate, then the limits and privacy caveat. No filler or repetition of the title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, no-output-schema tool it covers safety, quotas, and return behavior (a preview) well enough to call correctly. It stops short of saying what the preview contains or how quota-exceeded errors surface, which would fully close the loop.

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 coverage is 100%, so the baseline is 3, but the description adds real meaning for confirm: it explains the send/no-send consequence rather than restating 'true only after explicit user approval.' The other four parameters (jobId, candidateProfileId, subject, message) are left entirely to the schema.

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?

States a specific verb and resource ('Sends recruiter outreach to a talent-search candidate') and scopes the audience to talent-search candidates rather than applicants. It does not name or contrast with any sibling tool (e.g., find_candidates as the id source), so the differentiation is implied by scope rather than explicit.

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

Usage Guidelines4/5

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

Gives a clear operating procedure: call without confirm to preview, call with confirm=true to actually send, and the schema reinforces 'true only after explicit user approval.' No explicit when-not-to-use or named alternative is provided, which keeps it short of a 5.

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