Skip to main content
Glama

Add People to Audience Segment

add_to_segment
Idempotent

[Act · writes] Add one or more people (by person_id) to a manual audience segment. Existing members are silently ignored. Smart segments are rejected: their membership is computed from config by resolve_segment. Unknown person_ids are rejected as a whole (nothing is added). 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": "add_to_segment"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations, the description discloses three behaviors an agent could not infer: existing members are silently ignored, unknown person_ids cause the entire batch to be rejected with nothing added, and smart segments fail because membership comes from resolve_segment. It also states the call is free (0 credits), which matters for cost-sensitive planning.

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

Conciseness5/5

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

Four short sentences with the operation type and target resource front-loaded, followed by the membership rule, the failure modes and the cost. Nothing is repetitive and every sentence carries distinct 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 two-parameter mutation tool with no output schema, the description covers what the operation does, what it rejects, how silently ignored duplicates behave, and that it is free. An agent has everything needed to invoke it correctly and predict the outcome.

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 the parameters, their uuid formats and the 1-1000 batch limit are already documented in the schema. The description confirms person_id-based batching and all-or-nothing semantics but adds no new naming, format or default information. Baseline 3 applies.

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 gives a specific verb and resource ('Add one or more people ... to a manual audience segment') plus an operation tag '[Act · writes]', and it contrasts that with smart segments whose membership is computed by resolve_segment. An agent can distinguish this from remove_from_segment or add_to_collection 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 Guidelines4/5

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

It states the preconditions that decide whether to call it: the target must be a manual segment (smart segments are rejected) and the person ids must be known (unknown ids cause the whole call to fail). It does not name the inverse tool explicitly, but the conditions for valid use are clear.

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