Skip to main content
Glama
ptaramona

Conduyt MCP Server

by ptaramona
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

conduyt_bulk_delete_contacts_matching

Soft-delete every contact matching a list filter across all pages. Pass the filter and expected total to freeze the id set, then continue with remainingIds and the token until done.

Instructions

Soft-delete EVERY contact a list filter matches, across pages (#73, 2026-09-15) — the contacts page's "Select all N matching" action. FIRST CALL: pass the same filter you would give conduyt_list_contacts (search, tag, tags, source, reachability, company, company_id, assigned_to, created_from/to, updated_from/to, min_score, import_id, smart_view, smartListId, filters JSON, master_status, exclude_master_status, cf[key]) and expectedTotal = the meta.total that filter returned. The server re-counts and refuses when the set moved (409 expected_total_mismatch), refuses when some matching contacts are shared with you but not yours to delete (409 not_all_editable), then FREEZES the matching ids (max 50,000; 422 above) and deletes only those. Contacts with an upcoming appointment are kept (keptWithAppointments). If done=false the response carries remainingIds AND a signed continuation token: CALL AGAIN with ids = remainingIds and continuation = that token, verbatim (no filter, no expectedTotal) until done=true; busy=true means wait a moment first. The token is bound to you, this account and exactly those ids and expires after 2 hours (403 continuation_*); a continuation without it is refused. Empty filters are refused. Requires contacts:delete and an active subscription.

Input Schema

NameRequiredDescriptionDefault
idsNoContinuation: the remainingIds from the previous response, in the same order (send INSTEAD of filter/expectedTotal)
filterNoFirst call: the contact list filter parameters, exactly as for conduyt_list_contacts; at least one non-empty value
continuationNoContinuation: the `continuation` token from the previous response, verbatim (required with ids)
expectedTotalNoFirst call: the total the list showed for this filter (meta.total)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv4.71.0

TDQS

A4.4/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and delivers: 409 expected_total_mismatch and 409 not_all_editable refusal conditions, 50,000/422 cap, keptWithAppointments retention, token binding and 2-hour expiry (403 continuation_*), and required contacts:delete permission plus active subscription.

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?

Purpose is front-loaded and the dense continuation/error protocol is well-ordered. Length is justified by the multi-phase operation, though the filter/expectedTotal re-explanation overlaps with schema text.

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 complex, two-phase bulk mutation with no output schema, the description still documents return signals (done, remainingIds, continuation, busy, keptWithAppointments) and error codes, leaving nothing an agent needs to call it 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 coverage is 100% and the field descriptions already label ids/continuation as 'Continuation' and filter/expectedTotal as 'First call'. The description adds sequencing context (filter must equal what conduyt_list_contacts would take; expectedTotal equals meta.total) but largely restates the schema, so baseline 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?

States a specific verb (soft-delete), resource (every contact a list filter matches), and scope (across pages), and anchors it to the concrete UI action 'Select all N matching'. An agent can immediately tell this apart from id-based conduyt_bulk_delete_contacts.

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?

The two-phase flow is spelled out precisely: FILTER CALL with filter+expectedTotal, then continuation with ids+token, plus busy/true/403 handling. It does not explicitly compare against the sibling conduyt_bulk_delete_contacts (id-based delete), so the alternative routing is only implied.

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