Skip to main content
Glama

Update team

team_update
Destructive

Change a team's slug, title or description; what is left out stays. Named by its id, since its slug may be what changes. Requires a maintainer of the team or an organization owner. Recorded in the organization's audit log.

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>",
      "org": "<org>"
    },
    "name": "team_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe team's id, as team_list and team_get give it (team_9xyz).
orgYesslug of the organization whose people, teams and access to use. Required on every call, even when only one organization is listed; a path never names it.
slugNoA new slug for the team.
titleNoA new title.
descriptionNoA new description; null removes it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations supply readOnly=false and destructive=true, and the description adds context they cannot: omitted fields are left unchanged, the caller must be a team maintainer or org owner, and the change is written to the organization's audit log. It still omits what happens on a slug collision or duplicate title, and does not explain why the operation is flagged destructive.

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?

It is short, front-loaded with the mutation semantics, and every clause carries information. The semicolon-chained construction packs several distinct facts into one dense sentence, which slightly reduces scanability but wastes nothing.

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 five-parameter partial-update tool with no output schema, the definition covers mutations, authorization and audit consequences. Remaining gaps are error/conflict behavior on slug or title collisions, which matter since slugs are mutable and likely unique.

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; the description earns an extra point by stating that omitted parameters stay unchanged, which is the key semantic for the three optional fields. The id-vs-slug rationale also reinforces the required id parameter, though the schema already documents it.

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?

"Change a team's slug, title or description" states a specific verb plus the exact mutable fields, and the partial-update clause scopes it further. It is clearly distinguishable from siblings like team_create, team_get and team_setMaintainer 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 gives a real usage rule — address the team by id because the slug itself may change — plus prerequisites (maintainer of the team or organization owner). It does not name alternatives or exclusions, but the selective-update semantics make the when-to-use condition clear enough.

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