Skip to main content
Glama

Set team maintainer

team_setMaintainer
Destructive

Make someone on a team one of its maintainers, or a plain member again. 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": {
      "slug": "<slug>",
      "userId": "<userId>",
      "maintainer": "<maintainer>",
      "org": "<org>"
    },
    "name": "team_setMaintainer"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.
slugYesThe team's slug, as team_list gives it (platform).
userIdYesThe person's user id, as members_list gives it (user_2abc). Never a name or an email.
maintainerYestrue: a maintainer. false: a plain member.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, and the description adds genuinely useful context beyond them: the authorization requirement and that the change is written to the organization's audit log. It also implicitly reassures that the operation is reversible ('a plain member again'). It stops short of saying what the response contains or what happens on the last maintainer.

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?

Three short sentences, front-loaded with the action, then the permission gate, then the audit side effect. No filler and nothing buried.

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 four-required-parameter mutation with no output schema, the definition covers action, authorization, reversibility and audit trail, which is enough to call it correctly. The only real omission is the return shape and edge-case behavior (e.g., demoting the sole maintainer).

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%, so every parameter is already documented, including the maintainer boolean's true/false meaning and the org/slug/userId formats. The description adds only the framing that userId identifies a current team member; baseline 3 is appropriate when the schema carries the load.

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?

States a specific verb+resource pair: changing a team member's role between maintainer and plain member. It is clearly distinguishable from team_addMember/team_removeMember (membership changes) and team_update (team settings), though it never names those siblings explicitly.

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

Usage Guidelines3/5

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

The description supplies a real prerequisite ('Requires a maintainer of the team or an organization owner'), which tells the agent whether the call can succeed, and the 'or a plain member again' clause makes clear it handles both directions. It does not say when to prefer this over team_update or team_removeMember, so routing is only implied.

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