Generect

Submit a bulk job

start_bulk_job

Submit up to 50 records for asynchronous processing and get a job_id back. Billable at the same per-record rate as the single-record tool, and the whole cost is reserved at submit time: a submitted job keeps running (and charging) even if nobody polls it. Meant for a list the user has approved. get_bulk_job polls it, and a webhook (create_webhook) reports when it finishes.

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": {
      "job_type": "<job_type>",
      "items": "<items>"
    },
    "name": "start_bulk_job"
  }
}

Input Schema

Name	Required	Description
`mode`	No	Enrich jobs only: cached (cheaper) or live. Default "database".
`items`	Yes	Max 50. email_find/phone_find: {lead_id} \| {linkedin_url} \| {first_name,last_name,domain\|company}. enrich_leads: {id} \| {linkedin_url} \| {email}. enrich_companies: {id} \| {linkedin_url} \| {domain} \| {name}.
`job_type`	Yes	What to do with the items. phone_find is by far the most expensive per record.
`timeout_ms`	No	Request timeout in milliseconds.
`confirm_spend_usd`	No	Explicit approval for an unusually large charge. Calls whose worst case exceeds $5 are refused unless this is set to at least the amount the tool reports. Only set it after the user has agreed to that number.

Output Schema

Name	Required	Description	Default
`job`	No
`cost`	No
`mode`	No
`dropped`	No
`job_type`	No
`next_step`	No
`submitted`	No
`test_mode`	No
`reservation_note`	No
`test_mode_notice`	No
`vocabulary_warnings`	No
`reserved_worst_case_usd`	No
`deprecated_params_ignored`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 7, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

removedInput schema / additionalProperties
```
Removed value: -false
```
addedInput schema / properties / items / items / propertyNames
```
Added value: +{
+  "type": "string"
+}
```

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedOutput schema / properties / deprecated_params_ignored / propertyNames
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / vocabulary_warnings / items
```
Added value: +{}
```

Changed2 schema fields changedSep 24, 2026

addedInput schema / properties / confirm_spend_usd

Added value: +{
+  "description": "Explicit approval for an unusually large charge. Calls whose worst case exceeds $5 are refused unless this is set to at least the amount the tool reports. Only set it after the user has agreed to that number.",
+  "type": "number"
+}

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "cost": {
+      "additionalProperties": false,
+      "properties": {
+        "amount_charged_usd": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "billed": {
+          "type": "string"
+        },
+        "note": {
+          "type": "string"
+        },
+        "operation": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "deprecated_params_ignored": {
+      "additionalProperties": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "dropped": {
+      "type": "number"
+    },
+    "job": {},
+    "job_type": {
+      "type": "string"
+    },
+    "mode": {
+      "type": "string"
+    },
+    "next_step": {
+      "type": "string"
+    },
+    "reservation_note": {
+      "type": "string"
+    },
+    "reserved_worst_case_usd": {
+      "type": "number"
+    },
+    "submitted": {
+      "type": "number"
+    },
+    "test_mode": {
+      "type": "boolean"
+    },
+    "test_mode_notice": {
+      "type": "string"
+    },
+    "vocabulary_warnings": {
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

AddedSep 10, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Beyond the annotations (readOnly=false, destructive=false, openWorld=true) it discloses the billing model, the crucial fact that cost is reserved at submit time, and that an unpolled job keeps running and charging — the single most important gotcha for this tool. It also surfaces the $5 worst-case spend guard and the rule that confirm_spend_usd requires prior user agreement.

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?

Four sentences, front-loaded with the action and limit, then cost behavior, then the approval condition, then polling/webhook follow-up. No sentence is filler and each one carries a distinct fact.

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

Completeness5/5

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

For a billable async submission tool with an output schema and full schema coverage, the description covers everything an agent needs: item cap, async nature, cost reservation, spend approval gate, and how to observe completion. Return values are correctly left to the output schema.

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 coverage is 100% and the schema already documents items shape per job_type, the mode default, and the confirm_spend_usd contract, so the description only reinforces what is structured. It adds spend context that motivates confirm_spend_usd but contributes no parameter syntax or format detail the schema lacks.

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 and resource ("Submit up to 50 records for asynchronous processing") plus the immediate return ("get a job_id back"), and distinguishes itself from the single-record tool by naming the shared per-record billing. An agent can tell this apart from enrich_lead/find_phone without opening a schema.

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?

It gives a clear usage precondition ("Meant for a list the user has approved") and routes follow-up correctly to get_bulk_job for polling and create_webhook for completion notification. It stops short of an explicit "use the single-record tool when you have one item" exclusion, so the boundary is implied rather than stated.

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

All Generect 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.