--deprecated

This connector has been deprecated

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

Deliver Audience

deliver_audience

Destructive

Deliver an audience as a download using available organization subscription capacity. Required capacity depends on the selected records, attributes, and existing licenses. Supply template_id OR field_list — not both. Review the subscription capacity estimate from quote_delivery with the user before starting delivery. Returns delivery progress and signed download links once completed. Completion or failure may notify configured external webhooks and opted-in users by email; completion may also email the delivery creator and configured organization contacts. Requires 'creator' 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": {
      "audience_id": "<audience_id>",
      "destination": "<destination>"
    },
    "name": "deliver_audience"
  }
}

Input Schema

Name	Required	Description	Default
`field_list`	No	Custom list of field names (alternative to template_id)
`audience_id`	Yes	Audience to deliver
`destination`	Yes	Active delivery destination
`template_id`	No	Enrichment template ID from get_field_catalog()
`output_format`	No	Output file format for download deliveries. Omit to auto-detect: matched audiences default to their uploaded file format; all others default to csv.
`include_unmatched`	No	(matched subtype) Include rows that did not resolve to a real graph match — these get a best-effort derived iag_person_id (or null), not a real match. Defaults to true.
`output_compression`	No	Explicit download compression. gzip supports csv/json/jsonl; Avro uses native DEFLATE and rejects outer gzip. Never inherited from input compression.	none

Output Schema

Name	Required	Description
`cost`	Yes
`status`	Yes	Current delivery state
`guidance`	No	Interpretation or recovery guidance for this result
`count_unit`	No
`page_count`	No	Number of objects on this page, not the organization total
`audience_id`	Yes
`count_state`	No	Unknown means no count; available does not guarantee freshness. Recount for a current value.
`delivery_id`	Yes
`destination`	Yes
`next_actions`	No	Suggested next calls using returned IDs and available scopes. Not executed and not user consent.
`download_urls`	No	Fresh signed artifact URLs on an individual completed download delivery
`population_input`	No	Population input used for the preview; IDs refer to their current saved definitions

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 6, 2026
RemovedSep 27, 2026
AddedSep 26, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare destructiveHint=true, openWorldHint=true, and idempotentHint=false, yet the description adds substantial context beyond them: capacity consumption tied to records/attributes/licenses, signed download links returned on completion, and outbound webhook/email side effects to opted-in users, the creator, and org contacts. The required 'creator' scope is also disclosed, which the annotations do not cover.

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?

Front-loaded with purpose, then constraints, then side effects, then scope — a sensible ordering with no filler sentences. It is on the dense side at six sentences, and the webhook/email notification sentence is long, but each clause carries distinct operational information.

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?

For a destructive, open-world mutation with seven parameters and an output schema, the description covers what an agent needs: the pre-flight quote step, the template/field_list exclusivity, capacity implications, scope requirement, and notification side effects. Return values are handled by the output schema and only briefly referenced here, which is appropriate.

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, but the description adds a real constraint not encoded in the schema: template_id and field_list are mutually exclusive, choose one. That single sentence materially changes how an agent populates the parameters and justifies raising the score above baseline.

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?

States a specific verb (deliver), resource (audience), and mode (download via organization subscription capacity). It also names the prerequisite sibling quote_delivery, so an agent can place it in the workflow relative to quote_delivery, get_delivery, and deliver_file_match 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 Guidelines4/5

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

Gives explicit preconditions: review the capacity estimate from quote_delivery with the user before starting, and supply template_id OR field_list but not both. It also notes the required 'creator' scope. It stops short of stating when to prefer deliver_file_match or wait_for_delivery over this tool, so routing between sibling delivery tools is left partly to inference.

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?