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

List All Deliveries

list_all_deliveries
Read-onlyIdempotent

Search org delivery history across audiences with pagination. Supports status, destination, and audience_id filters, Use audience_id to narrow the search to one audience, or list_deliveries for its latest 100 deliveries. Signed download links are omitted; call get_delivery for one completed artifact. 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_all_deliveries"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum deliveries to return, 1–100 (default 25)
cursorNoOpaque pagination cursor from a previous response
statusNoOnly deliveries with this status
audience_idNoOnly deliveries for this audience
destinationNoOnly deliveries to this destination

Output Schema

NameRequiredDescriptionDefault
guidanceNoInterpretation or recovery guidance for this result
count_unitNo
deliveriesYesDelivery summaries; signed download URLs are omitted from history
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"
+    },
+    "deliveries": {
+      "description": "Delivery summaries; signed download URLs are omitted from history",
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "status": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "status"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "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"
+    }
+  },
+  "required": [
+    "deliveries"
+  ],
+  "type": "object"
+}
  2. Changed4 schema fields changed
    • addedInput schema / properties / audience_id / description
      Added value: +"Only deliveries for this audience"
    • addedInput schema / properties / destination / description
      Added value: +"Only deliveries to this destination"
    • addedInput schema / properties / limit / description
      Added value: +"Maximum deliveries to return, 1–100 (default 25)"
    • addedInput schema / properties / status / description
      Added value: +"Only deliveries with this status"
  3. First observed

TDQS

A4.3/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 safety profile is covered. The description adds two things annotations cannot: signed download links are omitted from results (explaining why get_delivery is needed), and the 'discovery' scope requirement. It does not discuss rate limits or result ordering, keeping it just short of the top mark.

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 scope statement is front-loaded and every sentence carries information (filters, alternatives, omission, auth). Minor deduction for the comma splice in "audience_id filters, Use audience_id" and the slightly run-on middle sentence, which cost a little readability but no substantive clarity.

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, return values need not be explained, and the description still flags the one surprising omission (no signed download links) plus the auth scope. Pagination mechanics are left to the cursor field documentation, which is reasonable for a list tool of this complexity.

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%, so limit, cursor, status, audience_id, and destination are already documented, including the enum values and the 1–100 bound. The description only restates which filters exist and that pagination is supported, adding no syntax or edge-case 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?

"Search org delivery history across audiences with pagination" gives a specific verb (search), resource (delivery history), and scope (org-wide, paginated). It explicitly separates itself from list_deliveries (per-audience latest 100) and get_delivery (single artifact), so an agent can choose without opening sibling schemas.

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

Usage Guidelines5/5

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

Names both alternatives and the conditions that select them: use audience_id here to narrow to one audience, use list_deliveries for its latest 100, and call get_delivery for one completed artifact. It also states the required 'discovery' scope, which is a real prerequisite for the call.

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