Skip to main content
Glama
Sign In

--deprecated

by ai.infiniteaudience.mcp
OverviewDiscussionsAdmin
This connector has been deprecated

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

Preview Saved Integration Segment

preview_saved_integration_segment
Read-onlyIdempotent

Preview exact unique identities, duplicate receipts, expiry/privacy exclusions, existing overlap, and net additions before creating or extending a segment. Returns an estimate for review before materialization. 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": "preview_saved_integration_segment"
  }
}

Input Schema

NameRequiredDescriptionDefault
filtersNoOptional provider, connection, run, source-kind, and time-window filters
target_segment_idNoOptional existing matched segment for overlap and net-addition counts

Output Schema

NameRequiredDescriptionDefault
previewYes
guidanceNoInterpretation or recovery guidance for this result
cutoff_atYes
count_unitNo
page_countNoNumber of objects on this page, not the organization total
count_stateNoUnknown means no count; available does not guarantee freshness. Recount for a current value.
next_actionsNoSuggested next calls using returned IDs and available scopes. Not executed and not user consent.
population_inputNoPopulation input used for the preview; IDs refer to their current saved definitions

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • 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"
+    },
+    "cutoff_at": {
+      "type": "string"
+    },
+    "guidance": {
+      "description": "Interpretation or recovery guidance for this result",
+      "type": "string"
+    },
+    "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": {
+      "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"
+    }
+  },
+  "required": [
+    "cutoff_at",
+    "preview"
+  ],
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / properties / filters / description
      Added value: +"Optional provider, connection, run, source-kind, and time-window filters"
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered; the description adds the non-obvious authorization requirement ("Requires 'discovery' scope") and clarifies the call is non-mutating and produces an estimate for review. It does not discuss cost, latency, or what happens when target_segment_id points to a stale segment.

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?

Three short sentences, front-loaded with the outputs, then the review-before-materialization purpose, then the scope prerequisite. Nothing is repeated and no sentence could be dropped without losing information.

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 and full parameter documentation, the description only needs to cover purpose, prerequisite, and behavioral character, all of which it does. The one loose thread is the tension between 'exact unique identities' and 'estimate,' which leaves the precision of the returned counts slightly ambiguous.

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%, including the filters object and target_segment_id's role, so the baseline is 3. The description reinforces that overlap and net-addition counts depend on an existing segment, but adds no syntax, format, or boundary semantics beyond what the schema already documents.

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 names a specific verb (preview) and resource (saved integration segment) and enumerates exactly what the preview computes: unique identities, duplicate receipts, expiry/privacy exclusions, overlap, and net additions. The clause 'Returns an estimate for review before materialization' cleanly separates it from the materializing sibling build_saved_integration_segment.

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?

'before creating or extending a segment' gives a clear triggering condition for when to call this instead of building directly. It stops short of naming the alternative tool explicitly or stating when-not to use it (e.g., for already-materialized segments), so it falls just short of full 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 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