Skip to main content
Glama
Sign In

Infinite Audience

by io.github.no-fait
OverviewDiscussionsAdmin

List File Match Jobs

list_file_match_jobs
Read-onlyIdempotent

List async file-based identity resolution jobs for the org. Each job corresponds to a matched segment created via create_segment(subtype=matched). Returns match_id, name, status, matching_status, input_record_count, match_count, match_rate, amount_charged, file_format, compression, segment_id, audience_id, audience_status, created_at, expires_at. amount_charged is null until this run first participates in a successful delivery, then shows its one-time pending match-usage estimate; it excludes delivery usage. audience_status (active/archived/null) reports whether the linked audience is still open-able in Library — job history itself always persists, even after the segment or audience is deleted. Cursor-paginated. Filter by status to find pending/active/failed jobs. Requires 'discovery' scope.

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum jobs to return (default 30, max 100)
beforeNoLegacy ISO timestamp cursor for pagination
cursorNoOpaque next_cursor from the preceding page; mutually exclusive with before
statusNoFilter by job status

Output Schema

NameRequiredDescriptionDefault
jobsYes
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_cursorNo
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 / before / description
      Previous value: -"ISO timestamp cursor for pagination"New value: +"Legacy ISO timestamp cursor for pagination"
    • addedInput schema / properties / cursor
      Added value: +{
+  "description": "Opaque next_cursor from the preceding page; mutually exclusive with before",
+  "type": "string"
+}
    • 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"
+    },
+    "jobs": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "match_id": {
+            "type": "string"
+          },
+          "status": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "match_id",
+          "status"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "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"
+    }
+  },
+  "required": [
+    "jobs",
+    "has_more"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare read-only/idempotent/non-destructive, and the description adds substantial context beyond them: amount_charged is null until the run participates in a successful delivery and excludes delivery usage, and job history persists even after the segment or audience is deleted. The scope requirement and cursor pagination are also disclosed.

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?

Purpose and the create_segment linkage are front-loaded, then return fields and caveats follow logically. It is dense but mostly earns its length; the amount_charged sentence is the one place that runs long relative to its decision value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, yet the description still names the returned fields and clarifies the two non-obvious ones (amount_charged, audience_status), plus the persistence guarantee. Nothing an agent needs to select and call this read tool is missing.

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 baseline is 3 and the schema already documents limit, cursor/before exclusivity, and the enum. The description adds intent-level meaning by explaining that status filtering is how you surface pending/active/failed jobs and that the tool is cursor-paginated.

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?

Specific verb+resource ('List async file-based identity resolution jobs for the org') with a precise linkage rule ('Each job corresponds to a matched segment created via create_segment(subtype=matched)'). It clearly distinguishes itself from the singular sibling get_file_match_job and from list_match_runs.

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?

States a concrete use case ('Filter by status to find pending/active/failed jobs') and a hard prerequisite ('Requires discovery scope'), which is real routing information. It does not explicitly name get_file_match_job as the alternative for single-job lookup, so the when-not is implied rather than stated.

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