--deprecated

This connector has been deprecated

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

Deliver File Match

deliver_file_match

Destructive

Trigger download delivery for a file-based identity match job. Always delivers to download — returns a signed URL to the enriched output file. Use this instead of deliver_audience for matched segments created via create_segment(subtype=matched). The match_id is the segment_id returned by create_segment(subtype=matched) — delivery still routes through an audience wrapper internally. Matched segments do not support LiveRamp or Narrative destinations. Supply template_id OR field_list — not both. Use get_field_catalog() to browse options. 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": {
      "match_id": "<match_id>"
    },
    "name": "deliver_file_match"
  }
}

Input Schema

Name	Required	Description	Default
`match_id`	Yes	The segment_id returned by create_segment(subtype=matched) — also accepted as match_id for backward compatibility
`field_list`	No	Custom list of field names to include. Mutually exclusive with template_id.
`template_id`	No	Enrichment template ID from get_field_catalog(). Mutually exclusive with field_list.
`webhook_url`	No	Optional HTTPS URL to notify when delivery completes.
`output_format`	No	Output file format. Defaults to csv if not specified.
`include_unmatched`	No	Include rows that did not resolve to a known identity. Defaults to true.
`output_compression`	No	Explicit output compression. gzip supports csv/json/jsonl; Avro uses native DEFLATE.	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.3/5.0

Behavior4/5

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

Annotations already declare destructive=true, idempotent=false, openWorld=true, but the description adds real value beyond them: the output is a signed URL to an enriched file, delivery routes through an audience wrapper internally, external webhooks and email notifications may fire to creators and org contacts, and 'creator' scope is required. The remaining gap is that, despite idempotentHint=false, it never warns that repeated calls may produce duplicate deliveries.

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 the core action and delivery behavior, then alternatives, then constraints, then permissions. Dense but every clause carries operational information; only the repetition of the matched-segment routing detail is mildly redundant.

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 destructive, non-idempotent delivery tool with 7 parameters, the description covers destination, return artifact, scope, exclusions, and notification side effects, and an output schema exists so return values need not be detailed. The one omission an agent would want is duplicate-delivery/idempotency behavior.

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 all seven parameters are already documented, including the mutual exclusivity of template_id and field_list and the match_id/segment_id backward-compatibility note. The description reinforces the either/or choice and the field catalog pointer but adds little syntax or format meaning beyond the schema, which is the expected 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 and resource ('Trigger download delivery for a file-based identity match job') and adds scope detail ('always delivers to download — returns a signed URL'). It explicitly distinguishes itself from the sibling deliver_audience, so an agent can route correctly without opening either schema.

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?

Gives explicit when-to-use guidance ('Use this instead of deliver_audience for matched segments created via create_segment(subtype=matched)') and two hard exclusions (no LiveRamp or Narrative destinations). It also prescribes parameter selection (template_id OR field_list) and points to get_field_catalog for discovery.

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?