Infinite Audience

Get Saved Integration Segment Build

get_saved_integration_segment_build

Read-onlyIdempotent

Check a saved-match segment materialization by materialization_id after build_saved_integration_segment. Returns aggregate progress/status and the durable segment ID once complete; it does not start another build. Requires 'discovery' scope.

Input Schema

Name	Required	Description	Default
`materialization_id`	Yes	Materialization ID returned by build_saved_integration_segment

Output Schema

Name	Required	Description
`mode`	Yes
`status`	Yes
`preview`	Yes
`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
`count_state`	No	Unknown means no count; available does not guarantee freshness. Recount for a current value.
`failure_code`	Yes
`next_actions`	No	Suggested next calls using returned IDs and available scopes. Not executed and not user consent.
`collection_id`	Yes
`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.
`identity_count`	Yes
`failure_message`	Yes
`population_input`	No	Population input used for the preview; IDs refer to their current saved definitions
`target_segment_id`	Yes
`materialization_id`	Yes

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": {
+    "collection_id": {
+      "type": "string"
+    },
+    "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"
+    },
+    "failure_code": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "failure_message": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "guidance": {
+      "description": "Interpretation or recovery guidance for this result",
+      "type": "string"
+    },
+    "identity_count": {
+      "anyOf": [
+        {
+          "type": "number"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "materialization_id": {
+      "type": "string"
+    },
+    "mode": {
+      "enum": [
+        "new_segment",
+        "add_to_segment"
+      ],
+      "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"
+    },
+    "preview": {
+      "anyOf": [
+        {
+          "additionalProperties": {},
+          "properties": {
+            "already_present": {
+              "type": "number"
+            },
+            "duplicate_observations": {
+              "type": "number"
+            },
+            "expired_identities": {
+              "type": "number"
+            },
+            "net_additions": {
+              "type": "number"
+            },
+            "source_observations": {
+              "type": "number"
+            },
+            "suppressed_identities": {
+              "type": "number"
+            },
+            "unique_identities": {
+              "type": "number"
+            }
+          },
+          "required": [
+            "source_observations",
+            "unique_identities",
+            "duplicate_observations",
+            "expired_identities",
+            "suppressed_identities",
+            "already_present",
+            "net_additions"
+          ],
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "status": {
+      "enum": [
+        "created",
+        "processing",
+        "completed",
+        "failed"
+      ],
+      "type": "string"
+    },
+    "target_segment_id": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "materialization_id",
+    "collection_id",
+    "mode",
+    "status",
+    "target_segment_id",
+    "preview",
+    "identity_count",
+    "failure_code",
+    "failure_message"
+  ],
+  "type": "object"
+}

First observedSep 26, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Beyond the readOnly/idempotent annotations, it discloses the required 'discovery' scope and what the call yields (aggregate progress/status plus the durable segment ID once complete). It does not describe what a partial/incomplete status looks like or whether repeated polling is expected, which would have pushed it higher.

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?

Two tight sentences: the identification/precondition comes first, the return contract and the negative constraint follow. Every clause carries information an agent would otherwise have to infer.

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 an output schema present, return values need not be spelled out, and the description still summarizes them; the scope requirement is a useful addition. It leaves minor gaps around polling behavior and the status vocabulary for a long-running check, but nothing essential for correct invocation.

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% and the schema already explains that materialization_id comes from build_saved_integration_segment, so the description's restatement adds little. Baseline 3 is appropriate for a single fully-documented parameter.

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 — check a saved-match segment materialization by materialization_id — and explicitly disambiguates from build_saved_integration_segment by noting it does not start another build. An agent can distinguish it from the build sibling without opening either schema.

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?

"after build_saved_integration_segment" gives a clear precondition for when to call it, and "it does not start another build" excludes the most likely misuse. There is no explicit mention of polling cadence or of an alternative (e.g. wait_for_segment-style blocking helper), 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 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?