100Hires MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

hires_send_candidate_message

Schedule candidate emails for a specific time or send immediately, with CC/BCC and reply threading options. If no time is set, the message is automatically scheduled 15 minutes ahead.

Instructions

Schedule an email message to a candidate. If scheduled_at is omitted, the message is scheduled for 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

Name	Required	Description
`cc`	No	Carbon-copy recipient email addresses.
`id`	Yes	Candidate ID (integer) or alias (string).
`to`	Yes	Primary recipient email addresses.
`bcc`	No	Blind carbon-copy recipient email addresses.
`body`	Yes	Email body as HTML.
`subject`	Yes	Email subject line.
`scheduled_at`	No	Unix timestamp (seconds) for when to send. Defaults to 15 minutes after creation.
`application_id`	No	Optional application ID to link this message to.
`from_account_id`	No	Sending mail account ID. If omitted, uses the API key owner's default mail account.
`reply_to_email_id`	No	Optional mailbox message ID to reply to.
`send_in_new_thread`	No	Send as a new email thread instead of replying in an existing one.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.3Aug 1, 2026

TDQS

A3.9/5.0

Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses the default scheduling behavior, which is valuable, but does not mention side effects (e.g., actual email send), permissions, or error handling. The scheduling nuance is disclosed, so it meets a minimum bar but lacks richer behavioral context.

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?

Two sentences, front-loaded with the primary action, and zero wasted words. It states the essential purpose and the key default behavior compactly.

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?

The description covers the core function and a critical default, but given 11 parameters and no annotations or output schema, it leaves some context implicit, such as the return value, prerequisites (e.g., valid candidate ID), and behavior on failure. However, the schema covers parameter details well, so the description is adequate but not comprehensive.

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?

The input schema has 100% coverage of all 11 parameters with descriptive text. The description adds the default timing for scheduled_at, but the schema already specifies this same detail. Therefore, the description does not provide significant added meaning beyond the schema.

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?

The description uses a clear verb ('Schedule') and resource ('email message to a candidate'), which precisely states the tool's function. It distinguishes itself from sibling tools by focusing on sending/scheduling messages to candidates, not other entities or list operations.

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 clearly communicates the scheduling context and the key default behavior (scheduled 15 minutes after creation if omitted). It does not explicitly state when to avoid this tool or mention alternatives, but the context is sufficiently clear for selecting it over generic message tools.

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

Deploy Server