Generect Live API MCP Server

Official

by generect

Overview Schema Source Related Servers Discussions(1)Admin

TypeScript

Hybrid

Manage webhook endpoints

manage_webhooks

Destructive

Register, update, delete, or test webhook endpoints for bulk-job completion events. Avoid long polling in scheduled workflows by letting completion events trigger jobs.

Instructions

List, create, update, delete or test webhook endpoints for bulk-job completion. FREE — this call never spends credits. Use this instead of long polling in scheduled/unattended workflows: register once, then let the completion event wake your job up.

Input Schema

TableJSON Schema

Name	Required	Description
`id`	No	Webhook id (required for update, delete, test).
`url`	No	HTTPS endpoint that receives events (create/update).
`action`	Yes	What to do.
`events`	No	Events to subscribe to (create/update).
`secret`	No	Shared secret for HMAC signature verification.
`timeout_ms`	No	Request timeout in milliseconds.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`cost`	No
`action`	No
`webhooks`	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

A4.3/5.0

Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=true, openWorldHint=true), it discloses a genuinely useful behavioral fact — 'FREE — this call never spends credits' — and explains the register-once/event-wake workflow model. It does not discuss HMAC secret handling, auth/permission needs, or rate limits, but the destructiveHint already covers the delete risk.

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 tight sentences: the action/resource inventory is front-loaded, then the cost and workflow guidance. The 'FREE' callout is placed prominently and nothing is repeated or padded.

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?

An output schema exists and schema coverage is complete, so return values and per-action field requirements need not be restated. The description supplies the missing framing (cost model, intended workflow, purpose) needed to call this multi-action tool correctly.

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 every parameter (id, url, action, events, secret, timeout_ms) is already documented in the schema. The description adds no syntax, format, or conditional-requirement detail beyond restating the action list, so the baseline of 3 applies.

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 names a precise set of actions (list, create, update, delete, test) on a specific resource (webhook endpoints) scoped to bulk-job completion events. No sibling tool touches webhooks, so an agent can immediately distinguish this from get_bulk_job or the bulk-job starters.

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 selection condition and names the alternative technique: 'Use this instead of long polling in scheduled/unattended workflows.' That routes the agent well, but it offers no 'when not to use' (e.g., interactive single-shot flows) and does not tie the five actions to any scenario guidance.

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

Deploy Server