100Hires - AI ATS & Recruitment Software

hires_batch_create_messages

Create up to 100 scheduled messages in one request; items are processed independently, one failure does not stop the others.

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": {
      "messages": "<messages>"
    },
    "name": "hires_batch_create_messages"
  }
}

Input Schema

Name	Required	Description	Default
`messages`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed15 schema fields changedSep 9, 2026
- removedInput schema / $schema
```
Removed value: -"http://json-schema.org/draft-07/schema#"
```
- removedInput schema / additionalProperties
```
Removed value: -false
```
- removedInput schema / properties / messages / description
```
Removed value: -"Array of message payloads to create (max 100)."
```
- removedInput schema / properties / messages / items / additionalProperties
```
Removed value: -false
```
- removedInput schema / properties / messages / items / properties / application_id / description
```
Removed value: -"Optional application ID linked to this message."
```
- removedInput schema / properties / messages / items / properties / bcc / description
```
Removed value: -"Blind carbon-copy recipient email addresses."
```
- changedInput schema / properties / messages / items / properties / body / description
```
Previous value: -"Email body as HTML."New value: +"HTML"
```
- removedInput schema / properties / messages / items / properties / candidate_id / description
```
Removed value: -"Target candidate ID for this message."
```
- removedInput schema / properties / messages / items / properties / cc / description
```
Removed value: -"Carbon-copy recipient email addresses."
```
- changedInput schema / properties / messages / items / properties / from_account_id / description
```
Previous value: -"Sending mail account ID. If omitted, the API key owner's default mail account is used."New value: +"Default: API key owner's default mail account"
```
- changedInput schema / properties / messages / items / 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 / messages / items / properties / scheduled_at / description
```
Previous value: -"Unix timestamp (seconds). If omitted, defaults to created time plus 900 seconds."New value: +"Unix seconds; default now + 900"
```
- changedInput schema / properties / messages / items / properties / send_in_new_thread / description
```
Previous value: -"Whether to send the message as a new thread instead of replying in an existing thread."New value: +"Start a new thread instead of replying"
```
- removedInput schema / properties / messages / items / properties / subject / description
```
Removed value: -"Email subject line."
```
- changedInput schema / properties / messages / items / properties / to / description
```
Previous value: -"Primary recipient email addresses."New value: +"Recipient emails"
```
First observedMay 9, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already show this is a write without destructiveHint, but the description adds a non-structured behavioral trait: 'one failure does not stop the others' – that per-item failure isolation is genuinely useful and not inferable from the schema or annotations. It also communicates that messages are scheduled ('scheduled messages'), another behavior trait. It does not cover rate limits, permission prerequisites, or partial-failure response format, but the presence of annotations and these additions justify a 4.

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 one sentence of substantive content: action, scale, and fault behavior. No filler, no redundancy, and the key constraint (up to 100) is front-loaded. 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?

With a complex nested array schema and no output schema, the description covers the core purpose, item count, and fault model, but omits what the caller sees on failure (per-item results?), potential permissions, and any additional scheduling defaults. It is good baseline for a batch-write but such a thorough tool needs a bit more detail to be fully complete.

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

Parameters2/5

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

Schema description coverage is 0% at the top level, and the description does not explain any of the nested properties (cc, bcc, from_account_id, etc.). With low schema coverage, the description carries more responsibility to clarify the messages array, but it only gives 'scheduled messages' context and the up-to-100 limit; it does not add meaning to any specific parameter. The agent must infer the semantics of `to`, `subject`, `body` and optional fields.

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 states a specific verb+resource ('Create ... scheduled messages'), the volume limit ('up to 100'), and the single-request scope, which clearly distinguishes it from single-send tools like hires_send_candidate_message. The title correctly completes the resource context, so no agent would confuse this with a non-batch or non-message tool.

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 explicit when/when-not guidance or mention of alternatives. The 'in one request' and 'up to 100' imply a batch use case, but the description never names hires_send_candidate_message or any other tool, nor does it say when the agent should stop 'favor' this over a single-send or scheduled message update. These are excluded endpoints that transition outside key meanings.

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 tools Inspect

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.