--deprecated

This connector has been deprecated

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

Archive Audience

archive_audience

DestructiveIdempotent

Archive a saved audience to hide it from the default list, or restore it with restore=true. Preserves its composition and delivery history. Requires the creator scope. 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>"
    },
    "name": "archive_audience"
  }
}

Input Schema

Name	Required	Description	Default
`restore`	No	True restores an archived audience to active
`audience_id`	Yes	Saved audience ID

Output Schema

Name	Required	Description
`status`	Yes
`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.
`next_actions`	No	Suggested next calls using returned IDs and available scopes. Not executed and not user consent.
`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

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already cover safety and idempotency (destructiveHint=true, idempotentHint=true), and the description adds genuinely non-obvious behavior: composition and delivery history are preserved, and the creator scope is required. It does not specify what happens when archiving an already-archived audience, but the idempotent annotation covers that.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded and short, but the scope requirement is stated twice in near-identical sentences ('Requires the creator scope. Requires 'creator' scope.'), which is wasted space and slightly muddies the requirement.

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

Completeness3/5

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

With an output schema present and full parameter documentation, this mostly suffices: mutation semantics, data preservation, and scope are all stated. However, for a destructive, reversible state toggle the description never says whether restore requires a different scope or what the archived audience's effect on existing deliveries/campaigns is.

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 coverage is 100%, so both audience_id and restore are already documented. The description mentions restore=true but only restates what the schema property already says ('True restores an archived audience to active'), adding no new format or edge-case meaning. Baseline 3 applies.

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 plus the observable effect: 'Archive a saved audience to hide it from the default list', and covers the inverse operation via restore=true. The audience-vs-segment distinction from the sibling archive_segment is carried by the resource noun rather than an explicit contrast.

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 clear context for each mode: archive when you want the audience hidden from the default list, and set restore=true to bring it back to active. No exclusion or 'use X instead' guidance is given, but the when-to-use condition is explicit.

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?