Skip to main content
Glama
This connector has been deprecated

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

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 subscription capacity source. Results are cursor-paginated. Supply at most one of provider, connection_id, kind, or status; use next_cursor to continue. 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": "list_integration_runs"
  }
}

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.
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"
      +    },
      +    "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. Changed5 schema fields changed
    • addedInput schema / properties / connection_id / description
      Added value: +"Filter to one organization integration connection"
    • addedInput schema / properties / kind / description
      Added value: +"Filter to one run kind"
    • addedInput schema / properties / limit / description
      Added value: +"Maximum runs per page, 1–100"
    • addedInput schema / properties / provider / description
      Added value: +"Filter to one integration provider"
    • addedInput schema / properties / status / description
      Added value: +"Filter to one run status"
  3. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the bar is lower, and the description still adds real context: intermediate workflow artifacts stay private, the projection records provenance/counts/selected fields/capacity source, and the call requires 'discovery' scope. That is meaningful disclosure about privacy posture and authorization beyond the structured fields.

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?

Five short sentences, front-loaded with the purpose before the filter and pagination rules; nothing is padded. The phrase about 'provenance, counts, selected fields, and subscription capacity source' is jargon-heavy and slightly opaque, but it still carries 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?

An output schema exists, so return values need not be explained, and the description covers pagination, the mutual-exclusivity rule, and the required scope. The remaining gap is the lack of an explicit pointer to get_integration_run for single-run lookups, which an agent would have to infer from the sibling list.

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 coverage is 100%, so the schema already documents each filter and its enum, making the baseline 3. The description adds a constraint the schema cannot express — that at most one of provider, connection_id, kind, or status may be supplied — which is genuinely useful invocation guidance, though it slightly muddles the cursor parameter by calling it 'next_cursor' while the schema names it 'cursor'.

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?

States a specific verb and resource ('List ... integration activity for this organization') and frames it as a safe, retained projection, which is enough to distinguish it from the singular get_integration_run sibling. It never names that sibling explicitly, so the differentiation is inferred rather than stated.

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?

Operational guidance is present: 'Supply at most one of provider, connection_id, kind, or status; use next_cursor to continue' plus the 'discovery' scope requirement. However, there is no guidance on when to choose this over get_integration_run, list_saved_integration_matches, or other list_* siblings, so usage context is only implied.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources