Generect Live API MCP Server

Official

by generect

Overview Schema Source Related Servers Discussions(1)Admin

TypeScript

Hybrid

Poll a bulk job (free)

get_bulk_job

Read-onlyIdempotent

Poll the status and retrieve results of a submitted bulk job using its job_id and job_type; polling never spends credits.

Instructions

Status and results of a bulk job. Free: this call never spends credits. Polling is free (the work was billed at submit time); a few seconds between polls is enough.

Input Schema

Name	Required	Description
`job_id`	Yes	job_id returned by start_bulk_job.
`job_type`	Yes	Same job_type used at submit.
`timeout_ms`	No	Request timeout in milliseconds.

Output Schema

Name	Required	Description	Default
`job`	No
`cost`	No
`job_id`	No
`results`	No
`job_type`	No
`test_mode`	No
`test_mode_notice`	No
`vocabulary_warnings`	No
`deprecated_params_ignored`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv0.12.2Oct 16, 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
```

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: +{}
```

Addedv0.9.0Sep 24, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already cover readOnly/idempotent, and the description adds genuinely new behavioral context: the call never spends credits and the billable work happened at submit time, so an agent knows repeated polling is safe and cost-free. It does not describe the possible job states (pending/failed/completed) or what happens on an unknown job_id, leaving some behavioral gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with what is returned followed by the cost/polling note. Slight redundancy between 'never spends credits' and 'Polling is free', but nothing is wasted overall.

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?

An output schema exists, so return values need no explanation, and the cost/polling guidance covers the main operational concern. The main missing piece is how to interpret status values and when to stop polling, which is a moderate rather than critical gap.

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 100%, so job_id, job_type and timeout_ms are already documented with their enum values and origin at submit. The description adds no parameter-level meaning, so baseline 3 applies.

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 first sentence names the resource (a bulk job) and what it returns (status and results), which separates it from start_bulk_job by referring to work 'billed at submit time'. It stops short of explicitly naming start_bulk_job as the counterpart, so differentiation is implied rather than stated.

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

Usage Guidelines3/5

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

The description gives an actionable polling cadence ('a few seconds between polls is enough') and states the call is free, which implies 'use this to poll after submitting'. However it never states when not to use it, how to know when to stop polling, or names start_bulk_job as the required predecessor.

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