Infinite Audience

List Saved Integration Matches

list_saved_integration_matches

List saved integration matches available to build into a segment. Returns aggregate counts without raw identities. Refreshes stored collection counts and may initialize collection metadata; does not create segments or charge for records. Use preview_saved_integration_segment before building. Requires 'discovery' scope.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`guidance`	No	Interpretation or recovery guidance for this result
`count_unit`	No
`page_count`	No	Number of objects on this page, not the organization total
`collections`	Yes
`count_state`	No	Unknown means no count; available does not guarantee freshness. Recount for a current value.
`next_actions`	No	Suggested next calls using returned IDs and available scopes. Not executed and not user consent.
`money_display`	No	Currency amounts formatted once from source paths ending in _cents. Use verbatim; do not divide again. Null/missing source amounts are omitted, not zero.
`population_input`	No	Population input used for the preview; IDs refer to their current saved definitions

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 26, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "collections": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "collection_id": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          },
+          "status": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "collection_id",
+          "name",
+          "status"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "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"
+    },
+    "money_display": {
+      "additionalProperties": {
+        "type": "string"
+      },
+      "description": "Currency amounts formatted once from source paths ending in _cents. Use verbatim; do not divide again. Null/missing source amounts are omitted, not zero.",
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "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"
+    },
+    "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"
+    }
+  },
+  "required": [
+    "collections"
+  ],
+  "type": "object"
+}

First observedSep 26, 2026

TDQS

A4.7/5.0

Behavior5/5

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

The description adds substantial behavioral detail beyond the annotations: it refreshes stored collection counts, may initialize collection metadata, does not create segments, and does not charge for records. It also discloses that results are aggregate counts without raw identities and that the 'discovery' scope is required.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core purpose and then adds precise operating constraints in a compact form. Every sentence contributes useful information about scope, side effects, or prerequisites.

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?

With no input parameters, an output schema present, and annotations covering safety hints, the description supplies the remaining context an agent needs: auth scope, side effects, aggregate-only returns, and the recommended preview step. Nothing material is missing for correct invocation.

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?

The tool has zero parameters, so there is no input semantics to explain; the schema coverage is effectively complete. Per the rubric, a zero-parameter tool has a baseline of 4 for this dimension.

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?

The description states a specific verb and resource: it lists saved integration matches available to build into a segment. It also distinguishes this from building by explicitly saying it does not create segments, and it names preview_saved_integration_segment as a related tool.

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?

It gives clear usage context by saying to use preview_saved_integration_segment before building, and it states the required 'discovery' scope. It does not explicitly map out every sibling alternative such as list_match_runs or list_integration_runs, so it stops short of full when-to-use guidance.

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

All Infinite Audience 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?