Skip to main content
Glama
Sign In

100Hires - AI ATS & Recruitment Software

by com.100hires
OverviewDiscussionsAdmin

hires_send_candidate_message

Schedule an email to a candidate; without scheduled_at it is sent 15 minutes after creation.

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": {
      "id": "<id>",
      "to": "<to>",
      "subject": "<subject>",
      "body": "<body>"
    },
    "name": "hires_send_candidate_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
ccNo
idYesCandidate id or alias
toYesRecipient emails
bccNo
bodyYesHTML
subjectYes
scheduled_atNoUnix seconds; default: now + 15 min
application_idNo
from_account_idNoMail account id; default: the API key owner's default account
reply_to_email_idNoMailbox message id to reply to
send_in_new_threadNoStart a new thread instead of replying

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed13 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / application_id / description
      Removed value: -"Optional application ID to link this message to."
    • removedInput schema / properties / bcc / description
      Removed value: -"Blind carbon-copy recipient email addresses."
    • changedInput schema / properties / body / description
      Previous value: -"Email body as HTML."New value: +"HTML"
    • removedInput schema / properties / cc / description
      Removed value: -"Carbon-copy recipient email addresses."
    • changedInput schema / properties / from_account_id / description
      Previous value: -"Sending mail account ID. If omitted, uses the API key owner's default mail account."New value: +"Mail account id; default: the API key owner's default account"
    • changedInput schema / properties / id / description
      Previous value: -"Candidate ID (integer) or alias (string)."New value: +"Candidate id or alias"
    • changedInput schema / properties / reply_to_email_id / description
      Previous value: -"Optional mailbox message ID to reply to."New value: +"Mailbox message id to reply to"
    • changedInput schema / properties / scheduled_at / description
      Previous value: -"Unix timestamp (seconds) for when to send. Defaults to 15 minutes after creation."New value: +"Unix seconds; default: now + 15 min"
    • changedInput schema / properties / send_in_new_thread / description
      Previous value: -"Send as a new email thread instead of replying in an existing one."New value: +"Start a new thread instead of replying"
    • removedInput schema / properties / subject / description
      Removed value: -"Email subject line."
    • changedInput schema / properties / to / description
      Previous value: -"Primary recipient email addresses."New value: +"Recipient emails"
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

The description discloses a key behavioral trait beyond the annotations: the 15-minute default delay when scheduled_at is not provided. This is valuable because the annotations only say readOnlyHint=false and destructiveHint=false, which don't convey the scheduling behavior. The description doesn't mention whether this creates a draft or sends immediately, but the scheduling detail is a meaningful behavioral disclosure.

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?

The description is a single sentence that front-loads the core purpose ('Schedule an email to a candidate') and immediately follows with the most important behavioral nuance (the 15-minute default). Every word earns its place; there is no fluff or repetition of schema details.

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 tool with 11 parameters and no output schema, the description is relatively complete but leaves gaps. It doesn't explain what the response looks like (e.g., the created message ID), whether the email is sent immediately or queued, or how to handle threading (send_in_new_thread). The 15-minute default is helpful, but an agent might need to know if the tool returns a scheduled message object or just a success status. Given the parameter count and no output schema, a bit more context would be warranted.

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 64%, so the schema documents most parameters. The description adds the crucial default for scheduled_at ('now + 15 min'), which is not fully explicit in the schema ('default: now + 15 min' is in the schema, but the description reinforces it). However, the description doesn't explain the semantics of parameters like application_id, reply_to_email_id, or send_in_new_thread beyond what the schema already provides. With 64% coverage, the description partially compensates but doesn't fully bridge the gap for undocumented parameters like cc, bcc, and application_id.

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?

The description states a specific verb and resource: 'Schedule an email to a candidate'. This clearly distinguishes it from message-related siblings like hires_batch_create_messages, hires_update_message, and hires_patch_message. It could be slightly clearer about whether it creates a new message vs. sends an existing one, but the verb 'schedule' and the schema fields (to, subject, body) make the core purpose clear.

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?

The description gives a clear context for when to use this tool: when you want to schedule an email to a candidate. It also explains the default behavior when scheduled_at is omitted. However, it doesn't explicitly state when NOT to use it or name alternatives like hires_batch_create_messages for bulk sending or hires_update_message for editing an existing message. The context is clear enough for an agent to select it for single-candidate email scheduling.

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

All 100Hires - AI ATS & Recruitment Software 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