Skip to main content
Glama
Sign In

LiveCRM

by ai.livecrm
OverviewDiscussionsAdmin

List Duplicate Groups

list_duplicate_groups
Read-only

List the duplicate groups detected on this connection, newest first. Each carries its status, how many records it holds, which one is the master, and a match score between 0 and 1. With no status the whole triage queue is returned except rejected groups; pass a status to narrow it, or a run_id to see only what one deduplication run found.

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": {
      "connection_id": "<connection_id>"
    },
    "name": "list_duplicate_groups"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many to return. Defaults to 50.
offsetNoSkip this many, for the next page. Default 0.
run_idNoOnly the findings owned by this run.
statusNoOnly groups in this status.
object_typeNoOnly groups of this object, or lead_to_contact for Lead to Contact groups.
connection_idYesThe CRM connection. Call list_crm_connections first.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / object_type / description
      Previous value: -"Only groups of this object."New value: +"Only groups of this object, or lead_to_contact for Lead to Contact groups."
    • changedInput schema / properties / object_type / enum
      Previous value: -[
-  "account",
-  "contact",
-  "lead"
-]New value: +[
+  "account",
+  "contact",
+  "lead",
+  "lead_to_contact"
+]
  2. Changed2 schema fields changed
    • addedInput schema / properties / object_type
      Added value: +{
+  "description": "Only groups of this object.",
+  "enum": [
+    "account",
+    "contact",
+    "lead"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / offset
      Added value: +{
+  "description": "Skip this many, for the next page. Default 0.",
+  "minimum": 0,
+  "type": "integer"
+}
  3. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish this is a safe read (readOnlyHint=true, destructiveHint=false) and closed-world. Beyond that, the description adds genuinely useful behavior: the default result set silently excludes Rejected groups, results are newest-first, and each row carries status, record count, master designation, and a 0-1 match score.

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 sentences, front-loaded with the core action and return contents before the filter explanation. The final sentence is slightly run-on with stacked clauses, but no sentence is filler.

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 usefully enumerates the fields each group carries and explains the default exclusion of Rejected. Pagination defaults live in the schema, so the omission is minor, though the newest-first ordering claim goes unqualified for paginated calls.

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%, so all six parameters are already documented, giving a baseline of 3. The description adds real meaning only for status omission (whole queue minus Rejected) and run_id scoping; limit, offset, object_type, and connection_id are left entirely to the schema.

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?

States a specific verb and resource: lists duplicate groups detected on a given connection, with an explicit ordering (newest first). It is distinguishable from the singular get_duplicate_group and from the count_* tools, though it never names an alternative explicitly.

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 filtering guidance: no status returns the whole triage queue, passing a status narrows it, and run_id restricts to a single run's findings. It does not say when to prefer get_duplicate_group or count_crm_records over this list, so it stops short of full when/when-not guidance.

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

All LiveCRM toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources