Skip to main content
Glama

conduyt_update_intake_deals

Configure automatic deal creation for live intake events like webhook upserts, form submissions, and bookings by setting the target pipeline, stage, and re-inbound policy.

Instructions

Configure automatic deal creation on LIVE intake (inbound webhook contact upserts, public form submissions, public bookings). When enabled, each ELIGIBLE intake event mints a deal in the chosen pipeline/stage stamped with the trigger's own source. Exclusions that apply even under reInbound 'always': bulk imports never mint, staff/calendar/dialer-created appointments never mint, an exact replay of the same occurrence never mints twice, a same-source event for the same contact+pipeline within 10 minutes is treated as a delivery retry and skipped, and a contact whose masterStatus is terminal (won/lost/abandoned/disqualified) gets no new intake deals. reInbound governs contacts that already exist: 'if_no_open' (default, recommended) also skips when the contact already has an open deal in that pipeline; 'never' mints only for brand-new contacts. Requires settings:edit.

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": {
      "enabled": "<enabled>",
      "pipelineId": "<pipelineId>",
      "stageId": "<stageId>"
    },
    "name": "conduyt_update_intake_deals"
  }
}

Input Schema

NameRequiredDescriptionDefault
enabledYesTurn automatic intake-deal creation on or off
stageIdYesStarting stage UUID within that pipeline
reInboundNoPolicy for contacts that already exist (default 'if_no_open')
pipelineIdYesPipeline UUID the intake deals land in (conduyt_list_pipelines)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv4.71.0

TDQS

A4.6/5.0
Behavior5/5

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

With zero annotations the description carries the full burden and delivers: it lists the exclusion set that applies even under 'always', discloses dedupe behavior (exact replay never mints twice; same-source event within 10 minutes treated as a delivery retry), describes terminal masterStatus handling, and states the required permission ('settings:edit'). This is far beyond what the schema conveys.

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?

Front-loads the purpose, then the exclusion rules, then parameter policy, then the permission requirement — a sensible ordering with no filler. The exclusion clause is a single very dense sentence that would read better broken up, which keeps it off a 5.

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 4-parameter configuration mutation with no annotations and no output schema, the description covers everything an agent needs: what activates, what is excluded, dedupe semantics, the reInbound trade-off, and the authorization prerequisite. Nothing material is missing.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3, but the description earns above baseline by explaining what each 'reInbound' mode actually means behaviorally (skips when an open deal exists in that pipeline; only mints for brand-new contacts) and by tying pipelineId/stageId to the 'chosen pipeline/stage' the deal lands in. This genuinely enriches the terse enum and parameter descriptions.

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?

States a specific verb ('Configure automatic deal creation') and an explicit resource scope ('LIVE intake') and enumerates the exact triggers: inbound webhook contact upserts, public form submissions, public bookings. No sibling tool in the list covers this same intake-automation surface, so it is clearly distinguishable.

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?

Gives concrete selection guidance for the tricky parameter ('reInbound': 'if_no_open' is the recommended default; 'never' only for brand-new contacts) and enumerates when the rule does NOT apply (bulk imports, staff/calendar/dialer appointments, terminal statuses). It stops short of naming alternative tools or stating the preconditions for choosing this over, e.g., pipeline or automation tools.

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

Deploy Server

Other Tools