Skip to main content
Glama

Remove People from Audience Segment

remove_from_segment
DestructiveIdempotent

[Act · writes · destructive] Remove one or more people (by person_id) from a manual audience segment. Missing members are silently ignored. Smart segments are rejected: their membership is computed from config by resolve_segment. Free — costs 0 credits.

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>",
      "person_ids": "<person_ids>"
    },
    "name": "remove_from_segment"
  }
}

Input Schema

NameRequiredDescriptionDefault
person_idsYesperson_ids to remove (1-1000 per call)
segment_idYesTarget segment id from list_segments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare destructive=true and idempotentHint=true, but the description adds non-obvious traits: missing members are silently ignored, smart segments fail by design, and calls cost 0 credits. That silent-ignore behavior in particular changes how an agent should interpret results.

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?

One tight paragraph that front-loads action, write, and destructive markers, then the scope constraint, then cost. The bracketed tag prefix partially restates annotations, which is minor redundancy rather than filler.

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 two-parameter mutation with full annotation coverage and no output schema, the description covers safety, scope, edge cases, and cost. It stops short of saying what a successful call returns (e.g., removed count), which is the only meaningful omission.

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 parameters and the 1-1000 array bound are already documented. The description adds only the person_id naming convention, which duplicates the schema rather than extending it with format or edge-case detail.

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 (Remove) and resource (people from a manual audience segment) with the keying (by person_id), and explicitly scopes out smart segments in the same breath. An agent can tell this apart from add_to_segment or resolve_segment without opening the schema.

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 a clear use condition (removing members from a manual segment) and an explicit exclusion (smart segments are rejected and belong to resolve_segment). It does not name the inverse tool add_to_segment, so routing to the write-side alternative is left to inference.

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