Skip to main content
Glama
This connector has been deprecated

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

Archive Segment

archive_segment
DestructiveIdempotent

Archive a segment to hide it from the default segment catalog and new audience compositions, or restore an archived one back to active. Archiving changes where the segment can be used; restoring it is a separate action. Archiving does not affect audiences that already reference this segment — their composition and record count are unchanged. This is distinct from permanently deleting a segment, which does change referencing audiences' composition and cannot be undone. 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": {
      "segment_id": "<segment_id>"
    },
    "name": "archive_segment"
  }
}

Input Schema

NameRequiredDescriptionDefault
restoreNoPass true to restore an archived segment back to active instead of archiving it
segment_idYesThe segment ID to archive or restore

Output Schema

NameRequiredDescriptionDefault
statusYes
guidanceNoInterpretation or recovery guidance for this result
count_unitNo
page_countNoNumber of objects on this page, not the organization total
segment_idYes
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. Added
  2. Removed
  3. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare a mutating, destructive, idempotent, closed-world operation, and the description contributes the important non-obvious fact that existing audiences referencing the segment are unaffected in composition or record count. Scope requirements and the reversibility contrast with deletion are stated. The one gap is that it never reconciles the destructiveHint=true annotation with a reversible archive/restore action, which could confuse an agent weighing risk.

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 important scoping and exclusion facts are front-loaded and the sentences are dense with information. It loses a point for the literal duplication at the end ('Requires the creator scope. Requires "creator" scope.'), which wastes space and reads as a generation artifact.

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 two-parameter mutation tool with full schema coverage, published annotations, and an output schema, the description covers purpose, side effects on referencing audiences, reversibility, the deletion contrast, and the authorization scope. Nothing material is missing for correct invocation.

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% and both parameters are already documented, so the baseline is 3. The description goes further by framing 'restore' as the inverse mode of the same tool ('restoring it is a separate action') rather than an independent capability, which clarifies why a single boolean flips the operation.

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?

The description opens with a specific verb and resource ('Archive a segment') and immediately scopes the effect: hidden from the default catalog and new compositions, with a restore path. It explicitly separates this from permanent deletion, so an agent can distinguish it from delete-like siblings without opening any 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?

It states both directions of use (archive vs. restore via the flag), the condition for choosing restore, and the key exclusion: this is not deletion, and deleted behavior cannot be undone. The creator-scope prerequisite is also given, leaving little to infer.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources