Skip to main content
Glama
Sign In

twelvebit Analytics

by app.twelvebit
OverviewDiscussionsAdmin

Remove someone from the site

remove_team_member
DestructiveIdempotent

Remove a person from the site (owner only). The API keys they made for this site stop working. Needs confirm: true; without it the tool only shows what it would do.

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": {
      "email": "<email>"
    },
    "name": "remove_team_member"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteNoSite domain (example.com), id or public id (tb_…). Optional with a site key, or when the account has one site.
emailYes
confirmNoSet to true to really do it. Without it, the tool only describes what it would do.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Goes well beyond the annotations by naming the caller requirement (owner), the concrete downstream effect (the person's API keys for the site stop working), and the dry-run behavior without confirm: true. It does not say whether the removal is reversible or what happens on a repeat call for an already-removed member, which matters for a destructive tool.

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 and permission gate, then consequences, then the confirmation requirement. Every sentence carries information the agent needs; nothing is padded.

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 3-parameter destructive mutation with no output schema, it covers permission, side effects, and the confirm gate—enough to call it correctly and safely. Missing only edge-case behavior such as a non-existent or already-removed member and error/return expectations.

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 67%, and the confirm parameter is already documented in the schema with the same semantics the description restates. The description adds the 'must be true to really do it' safety framing but says nothing about the email parameter or when site can be omitted. Baseline 3 is appropriate given a partially documented schema.

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 and resource ('Remove a person from the site'), and the parenthetical '(owner only)' plus the API-key side effect differentiate it from invite_team_member and update_team_member. An agent can pick this over its siblings without inspecting schemas.

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?

Explicitly scopes usage by permission level ('owner only') and describes the two-step confirm pattern, which effectively tells the agent how to proceed safely. No explicit exclusion or named alternative (e.g., use update_team_member to change a role instead of removing), so it falls short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All twelvebit Analytics toolsInspect
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