Skip to main content
Glama

conduyt_list_deals

List deals filtered by pipeline, stage, assignee, or status. Returns deal titles, values, stages, contacts, and dates; resolves names to UUIDs with clear errors for invalid names.

Instructions

List deals with filtering by pipeline, stage, assignee, or status. Returns deal title, value, stage, contact, and dates. Filter by pipeline/stage NAME (the same names you import with) or by UUID — both camelCase (pipelineName) and snake_case (pipeline_name) argument names are accepted. An unknown name returns a clear error, never the whole account.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "conduyt_list_deals"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (default 1)
stageNoFilter by stage UUID (canonical). Aliases: stageId, stage_id.
searchNoSearch deal titles
statusNoFilter by deal status
stageIdNoFilter by stage UUID (alias of stage).
per_pageNoResults per page (default 25, max 100)
pipelineNoFilter by pipeline UUID (canonical). Aliases: pipelineId, pipeline_id.
stage_idNosnake_case alias of stageId.
stageNameNoFilter by stage NAME within the pipeline — resolved to its UUID; errors if not found. Alias: stage_name.
assignedToNoFilter by assigned user UUID
pipelineIdNoFilter by pipeline UUID (alias of pipeline).
stage_nameNosnake_case alias of stageName.
pipeline_idNosnake_case alias of pipelineId.
pipelineNameNoFilter by pipeline NAME (the same name used in conduyt_import_deals/create) — resolved to its UUID; errors if not found. Alias: pipeline_name.
pipeline_nameNosnake_case alias of pipelineName.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv4.71.0

TDQS

A3.8/5.0
Behavior4/5

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

No annotations exist, so the description must carry the load; it discloses return fields, name-to-UUID resolution semantics, and — importantly — that an unknown name errors out rather than silently returning the whole account, which bounds a dangerous failure mode. It omits pagination/sorting behavior and whether results are ordered, leaving some 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?

Three front-loaded sentences with no filler; the purpose and return shape come first, then the name/UUID resolution caveat. Minor redundancy with the schema's alias documentation, but nothing wasted.

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?

With no output schema, the description compensates by naming the returned fields, and it addresses the trickiest aspect of a 15-parameter tool (name-vs-UUID resolution and error behavior). Pagination defaults, result ordering, and total-count behavior are left to the schema, which is a modest gap for a list endpoint.

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 the baseline is 3, but the description adds real meaning: it explains that pipeline/stage names are resolved to UUIDs and that both camelCase and snake_case argument names are accepted, tying the alias sprawl in the schema to intent. It does not cover page/per_page or search semantics, which remain schema-only.

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?

Opens with a specific verb+resource ('List deals') and enumerates the filterable dimensions, plus states the returned fields. It is clearly distinct from conduyt_get_deal, though it does not explicitly name that sibling or other listing alternatives (deal views, search).

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 useful in-tool guidance (filter by NAME or UUID, alias forms, unknown-name errors) but never says when to pick this over conduyt_get_deal, conduyt_list_deal_views, or conduyt_search. Usage is implied by the enumeration of filters rather than by explicit routing.

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