--deprecated

This connector has been deprecated

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

Update Segment

patch_segment

Destructive

Edit segment name, description or labels, or replace a filter segment definition. Supply filters OR filter_groups, never both. record_limit=null removes a size limit; a positive limit requires bounded State, City, or ZIP Code geography. Definition changes create a new version; renaming does not. Use archive_segment to archive or restore. 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": "patch_segment"
  }
}

Input Schema

Name	Required	Description
`name`	No	New display name
`labels`	No	Descriptive labels; an empty array clears them
`filters`	No	Replacement AND-combined filters (filter subtype only)
`segment_id`	Yes	Saved segment ID
`description`	No	Human description; null clears it without changing membership
`record_limit`	No	Maximum population size (up to 1 billion); null removes the limit
`filter_groups`	No	Replacement grouped filters (filter subtype only)

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
`segment_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

A4.5/5.0

Behavior5/5

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

Goes well past the annotations: it discloses that definition changes create a new version while renaming does not, that record_limit=null removes the size cap, that a positive limit requires bounded State/City/ZIP geography, and that the creator scope is required. These are non-obvious side effects and preconditions an agent could not infer from destructiveHint=true and idempotentHint=false alone.

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?

Dense, front-loaded, and every sentence carries operational content. The one flaw is the redundant closing pair "Requires the creator scope. Requires 'creator' scope." — the same requirement stated twice, which should be a single clause.

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?

Covers scope requirements, versioning side effects, and filter-shape constraints for a seven-parameter mutation tool, and an output schema means return values need not be described. The missed piece is partial-update semantics: whether an unspecified name/labels/filters clears the existing value or preserves it.

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%, so the baseline is 3, but the description adds real meaning beyond the schema: the filters/filter_groups exclusivity, the null-versus-positive semantics of record_limit, and the geography constraint tied to a positive limit. It does not clarify whether omitted fields are left untouched versus cleared, which is the one semantic a PATCH caller most needs.

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 plus resource and enumerates exactly which attributes are editable (name, description, labels) versus which are wholesale replaced (filter definition). It also names archive_segment as the tool that handles archive/restore, so an agent can separate the two 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 Guidelines4/5

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

Gives a hard mutual-exclusion rule ("Supply filters OR filter_groups, never both") and routes archiving/restoring to archive_segment. It does not discuss the boundary with other segment-mutating siblings such as refresh_segment, duplicate_segment, or create_segment, so the routing is clear for the archival case but not exhaustive.

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?