--deprecated

This connector has been deprecated

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

Get Integration Run

get_integration_run

Read-onlyIdempotent

Get one retained integration run by run_id. Returns customer-safe provenance, selected fields, record counts, processing status, and subscription capacity source; intermediate workflow artifacts are not exposed. Use an ID from list_integration_runs. Requires 'discovery' scope.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "run_id": "<run_id>"
    },
    "name": "get_integration_run"
  }
}

Input Schema

Name	Required	Description	Default
`run_id`	Yes	Integration run ID returned by list_integration_runs

Output Schema

Name	Required	Description
`kind`	Yes
`counts`	Yes
`run_id`	Yes
`status`	Yes
`guidance`	No	Interpretation or recovery guidance for this result
`provider`	Yes
`count_unit`	No
`created_at`	Yes
`page_count`	No	Number of objects on this page, not the organization total
`updated_at`	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.
`connection_id`	Yes
`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 changedNov 6, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "connection_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"
+    },
+    "counts": {
+      "additionalProperties": {
+        "type": "number"
+      },
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "created_at": {
+      "type": "string"
+    },
+    "guidance": {
+      "description": "Interpretation or recovery guidance for this result",
+      "type": "string"
+    },
+    "kind": {
+      "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"
+    },
+    "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"
+}

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 declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds real context beyond that: the run must be "retained", only customer-safe provenance and selected fields are surfaced, intermediate workflow artifacts are hidden, and a 'discovery' scope is required. It stops short of describing failure behavior for a non-retained or unknown run_id.

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: what it does first, what it returns and hides second, prerequisites last. No redundant or filler wording, and the identifying constraint is front-loaded.

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?

For a single-parameter read tool with a full output schema and complete annotations, the definition covers scope, return content boundaries and the auth scope an agent must satisfy. The only gap is behavior on expired or missing runs, which would be useful but is not essential given the rich structured fields.

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 coverage is 100% and the single run_id parameter is fully documented as coming from list_integration_runs. The description restates that same provenance and adds only the "retained" qualifier, which does not add format, syntax or validation meaning beyond the schema. Baseline 3 applies.

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?

"Get one retained integration run by run_id" gives a specific verb, resource and scope, and the following sentence names exactly what comes back (provenance, record counts, status, capacity source). It is clearly distinguishable from list_integration_runs and the other get_* siblings because it is keyed to a single run ID.

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?

"Use an ID from list_integration_runs" and "Requires 'discovery' scope" give concrete preconditions and point at the correct sibling for obtaining the identifier. There is no explicit when-not or fallback case (e.g., what to do for expired runs), so it falls short of a 5.

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?