--deprecated

This connector has been deprecated

Replaced by io.github.no-fait/infinite-audience

List Match Runs

list_match_runs

Read-onlyIdempotent

List past micro-batch identity match calls for the org. Returns run_id, match_count, match_rate, field_list, created_at, and expires_at. Results are cursor-paginated — pass next_cursor as cursor to fetch older pages. The before timestamp is a legacy alternative. Reported subscription capacity consumption is an estimate in USD; final rated consumption may differ. Use to audit recent match activity, inspect subscription capacity consumption, or find a specific run by scanning pages. Requires 'discovery' scope.

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": "list_match_runs"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Maximum runs to return (default 30, max 100)
`before`	No	Legacy ISO timestamp cursor — returns runs created before this time. Use the created_at of the last run in a previous response to paginate.
`cursor`	No	Opaque next_cursor from the preceding page; mutually exclusive with before

Output Schema

Name	Required	Description
`runs`	Yes
`guidance`	No	Interpretation or recovery guidance for this result
`has_more`	Yes
`count_unit`	No
`page_count`	No	Number of objects on this page, not the organization total
`count_state`	No	Unknown means no count; available does not guarantee freshness. Recount for a current value.
`next_cursor`	No
`next_actions`	No	Suggested next calls using returned IDs and available scopes. Not executed and not user consent.
`population_input`	No	Population input used for the preview; IDs refer to their current saved definitions

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 6, 2026

changedInput schema / properties / before / description

Previous value: -"ISO timestamp cursor — returns runs created before this time. Use the created_at of the last run in a previous response to paginate."New value: +"Legacy ISO timestamp cursor — returns runs created before this time. Use the created_at of the last run in a previous response to paginate."

addedInput schema / properties / cursor

Added value: +{
+  "description": "Opaque next_cursor from the preceding page; mutually exclusive with before",
+  "type": "string"
+}

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "count_state": {
+      "description": "Unknown means no count; available does not guarantee freshness. Recount for a current value.",
+      "enum": [
+        "unknown",
+        "available"
+      ],
+      "type": "string"
+    },
+    "count_unit": {
+      "const": "records",
+      "type": "string"
+    },
+    "guidance": {
+      "description": "Interpretation or recovery guidance for this result",
+      "type": "string"
+    },
+    "has_more": {
+      "type": "boolean"
+    },
+    "next_actions": {
+      "description": "Suggested next calls using returned IDs and available scopes. Not executed and not user consent.",
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "arguments": {
+            "additionalProperties": {},
+            "propertyNames": {
+              "type": "string"
+            },
+            "type": "object"
+          },
+          "reason": {
+            "type": "string"
+          },
+          "tool": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "tool",
+          "arguments",
+          "reason"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "next_cursor": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "page_count": {
+      "description": "Number of objects on this page, not the organization total",
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "population_input": {
+      "additionalProperties": {},
+      "description": "Population input used for the preview; IDs refer to their current saved definitions",
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "runs": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "input_record_count": {
+            "type": "number"
+          },
+          "match_count": {
+            "type": "number"
+          },
+          "run_id": {
+            "type": "string"
+          },
+          "status": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "run_id",
+          "status",
+          "input_record_count",
+          "match_count"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "runs",
+    "has_more"
+  ],
+  "type": "object"
+}

First observedSep 24, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive and closed-world behavior, so the description is only required to add context. It does: 'discovery' scope requirement, cursor pagination semantics with next_cursor, and the caveat that reported capacity consumption is an estimated USD figure that may be re-rated.

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?

Information is front-loaded: resource and return fields first, then pagination mechanics, caveats, and usage. Slightly dense, and the returned-field list partially duplicates the output schema, but no sentence is wasted.

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 three-parameter read-only list tool with a full output schema, the description covers everything an agent needs: scope requirement, pagination protocol, legacy-parameter handling, and the estimate caveat on consumption values.

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 the schema already documents limit, before and cursor, including mutual exclusivity. The description reinforces the cursor loop ('pass next_cursor as cursor') and labels before as a legacy alternative, which adds modest meaning over the schema rather than new syntax details.

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 and resource — 'List past micro-batch identity match calls for the org' — and the object fields returned (run_id, match_count, match_rate, field_list, created_at, expires_at). It is clearly distinguishable from the singular get_match_run sibling.

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?

Names three concrete use cases: auditing recent match activity, inspecting subscription capacity consumption, and locating a specific run by scanning pages. It does not explicitly name get_match_run as the alternative when the run_id is already known, which would complete the routing guidance.

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

All --deprecated tools Inspect

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

Need Help?