Skip to main content
Glama

Update segment

update_segment
Destructive

Rename a segment or replace its rules.

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": {
      "id": "<id>"
    },
    "name": "update_segment"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesSegment id
nameNoSegment name
matchNoall: a contact must match every rule. any: at least one ruleall
rulesNoUp to 10 rules that decide who matches
descriptionNoWhat the segment is for

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / description / description
      Added value: +"What the segment is for"
    • addedInput schema / properties / match / description
      Added value: +"all: a contact must match every rule. any: at least one rule"
    • addedInput schema / properties / name / description
      Added value: +"Segment name"
    • addedInput schema / properties / rules / description
      Added value: +"Up to 10 rules that decide who matches"
  2. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=false and readOnlyHint=false, so the safety profile is covered. The word 'replace' usefully signals that the rules array overwrites existing rules rather than merging, but the description says nothing about reversibility, permissions, or that omitted fields are left untouched.

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?

A single front-loaded sentence with zero filler; the two updateable surfaces are named immediately. Nothing to trim and nothing awkwardly buried.

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?

For a destructive 5-parameter mutation the description is thin, though the schema and annotations carry most of the load. It stops short of confirming that rules replacement is total and irreversible in effect, which is the one behavior an agent most needs before calling it.

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 description coverage is 100% and the nested rule schema is thoroughly documented, so the baseline is 3. The description adds only that 'name' and 'rules' are the updatable surfaces, omitting 'match', 'description' and the required 'id'.

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?

The description gives a specific verb plus resource ('Rename a segment or replace its rules') and is clearly distinguishable from create_segment, get_segment and delete_segment. It is slightly incomplete in that the tool can also change 'match' and 'description', which the sentence never mentions.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

No guidance on when to use this versus create_segment, preview_segment, get_segment or delete_segment, and no prerequisites or caveats stated. The agent must infer the usage context from the sibling list alone.

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.