Skip to main content
Glama
Sign In

Infinite Audience

by io.github.no-fait
OverviewDiscussionsAdmin

List Integration Runs

list_integration_runs
Read-onlyIdempotent

List safe, retained integration activity for this organization. Intermediate workflow artifacts stay private, while this projection records provenance, counts, selected fields, and billing rail. Results are cursor-paginated. Supply at most one of provider, connection_id, kind, or status; use next_cursor to continue. Requires 'discovery' scope.

Input Schema

NameRequiredDescriptionDefault
kindNoFilter to one run kind
limitNoMaximum runs per page, 1–100
cursorNoOpaque next_cursor from an earlier response
statusNoFilter to one run status
providerNoFilter to one integration provider
connection_idNoFilter to one organization integration connection

Output Schema

NameRequiredDescriptionDefault
runsYes
guidanceNoInterpretation or recovery guidance for this result
has_moreYes
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_cursorYes
next_actionsNoSuggested next calls using returned IDs and available scopes. Not executed and not user consent.
money_displayNoCurrency amounts formatted once from source paths ending in _cents. Use verbatim; do not divide again. Null/missing source amounts are omitted, not zero.
population_inputNoPopulation input used for the preview; IDs refer to their current saved definitions

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / kind / enum
      Previous value: -[
-  "enrichment",
-  "onboarding",
-  "activation",
-  "sync",
-  "file_match",
-  "delivery"
-]New value: +[
+  "batch_enrichment",
+  "file_enrichment",
+  "ingest",
+  "activation",
+  "export"
+]
    • changedInput schema / properties / status / enum
      Previous value: -[
-  "created",
-  "processing",
-  "awaiting_provider_writeback",
-  "completed",
-  "failed",
-  "expired"
-]New value: +[
+  "created",
+  "processing",
+  "awaiting_boundary",
+  "settling",
+  "completed",
+  "failed",
+  "cancelled"
+]
    • 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"
+    },
+    "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"
+    },
+    "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": {
+          "connection_id": {
+            "type": "string"
+          },
+          "counts": {
+            "additionalProperties": {
+              "type": "number"
+            },
+            "propertyNames": {
+              "type": "string"
+            },
+            "type": "object"
+          },
+          "created_at": {
+            "type": "string"
+          },
+          "kind": {
+            "type": "string"
+          },
+          "provider": {
+            "type": "string"
+          },
+          "run_id": {
+            "type": "string"
+          },
+          "status": {
+            "type": "string"
+          },
+          "updated_at": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "run_id",
+          "provider",
+          "connection_id",
+          "kind",
+          "status",
+          "counts",
+          "created_at",
+          "updated_at"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "runs",
+    "has_more",
+    "next_cursor"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior. The description adds meaningful context beyond that: intermediate workflow artifacts remain private, results are cursor-paginated, and the caller needs 'discovery' scope. It does not cover rate limits or response shape, but with annotations present this is solid additional disclosure.

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?

The description is compact and front-loads the core list operation, then layers in privacy, pagination, filter exclusivity, and scope. The phrasing 'safe, retained integration activity' is slightly abstract, but every sentence contributes to correct invocation.

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?

An output schema exists, so the description needn't document return fields, and annotations already carry the safety profile. The description covers the key non-schema constraints: one-filter-only, cursor pagination, discovery scope, and artifact privacy. The main remaining gap is sibling-usage guidance, which is minor but real.

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?

Schema description coverage is 100%, so the baseline is 3. The description adds an important cross-parameter rule not expressed in the schema: at most one of provider, connection_id, kind, or status may be supplied. The only minor wrinkle is that it says 'next_cursor' while the parameter is named 'cursor', though the schema clarifies the connection.

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?

The description clearly frames a list operation over integration activity for the organization, and adds useful scope details like provenance, counts, selected fields, and billing rail. It does not explicitly differentiate this tool from sibling list tools such as list_match_runs or get_integration_run, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives a concrete invocation constraint: 'Supply at most one of provider, connection_id, kind, or status' and tells the caller to use next_cursor to continue. However, it does not say when to use this tool instead of nearby siblings like get_integration_run or list_saved_integration_matches, leaving selection guidance implied rather than explicit.

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

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