Tokenrip

Add workspace member

workspace_member_add

Destructive

Add or invite someone to the workspace (member: an email, alias or account id) as editor (default: reads, writes and shares everything in it) or viewer (reads everything). Everyone in a workspace sees all of it. An email no verified person holds becomes an invite: the result has status 'invited' and an inviteUrl that is safe to share with them. Anyone who may share here (editors, guests included) may add; adding an existing member with another role changes it. Tokenrip emails a new invite or member, naming as inviter the verified address of the person who owns your account (inviting again with the same access resends an invite, at most once an hour). A member added by alias or id is emailed only when their account has exactly one verified person and yours has one to send from. note (at most 280 characters) goes in the email to an existing person and on the invite page for a new address; it is refused when no email is sent. An email add is refused NO_OPERATOR or OPERATOR_AMBIGUOUS when your account has no single verified person to name as inviter (an alias or id add then goes ahead without an email). RATE_LIMITED past the hourly invite email limits, which count the person's emails from all their accounts: an add of an existing account by alias or id without a note then goes ahead without the email; invites to new addresses, any add by email, and adds with a note are refused.

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": {
      "workspaceId": "<workspaceId>",
      "member": "<member>"
    },
    "name": "workspace_member_add"
  }
}

Input Schema

Name	Required	Description
`why`	No	Required for workspace items: one sentence on what the person is trying to accomplish, in their terms, not a description of this edit. Every workspace write takes one; sessions and summaries record themselves from it. At most 300 characters.
`note`	No	A short note for the invite, at most 280 characters; refused when the add sends no email.
`role`	No	editor (the default: reads, writes and shares everything in the workspace) or viewer (reads everything).
`member`	Yes	Who to add: an email address (an invite when no verified person holds it), an alias, or an account id.
`workspaceId`	Yes	The workspace: its id or its slug.

Output Schema

Name	Required	Description	Default
`member`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 12, 2026

removedInput schema / properties / membership

Removed value: -{
-  "description": "external only: a person added to a workspace is a guest (shared items only); internal access comes from owning the workspace or being in its team, so internal is refused INTERNAL_NEEDS_TEAM. Optional: everyone added is a guest.",
-  "enum": [
-    "internal",
-    "external"
-  ],
-  "type": "string"
-}

changedInput schema / properties / role / description

Previous value: -"editor (the default) or viewer."New value: +"editor (the default: reads, writes and shares everything in the workspace) or viewer (reads everything)."

Changed1 schema field changedNov 3, 2026

changedInput schema / properties / note / description

Previous value: -"A short note for the invite email, at most 280 characters; refused when the add sends no email."New value: +"A short note for the invite, at most 280 characters; refused when the add sends no email."

Changed1 schema field changedOct 27, 2026

changedInput schema / properties / membership / description

Previous value: -"internal (the default: sees everything) or external (shared items only)."New value: +"external only: a person added to a workspace is a guest (shared items only); internal access comes from owning the workspace or being in its team, so internal is refused INTERNAL_NEEDS_TEAM. Optional: everyone added is a guest."

Changed5 schema fields changedOct 24, 2026

changedInput schema / properties / workspaceId / description

Previous value: -"The workspace id (UUID)."New value: +"The workspace: its id or its slug."

removedInput schema / properties / workspaceId / format
```
Removed value: -"uuid"
```
addedInput schema / properties / workspaceId / maxLength
```
Added value: +64
```
addedInput schema / properties / workspaceId / minLength
```
Added value: +1
```

removedInput schema / properties / workspaceId / pattern

Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"

First observedOct 23, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Beyond the annotations (destructive=true, openWorld=true, idempotent=false), the description discloses a great deal: invite vs membership outcome, the returned status and inviteUrl, email-side effects and their hourly resend limit, and the NO_OPERATOR / OPERATOR_AMBIGUOUS / RATE_LIMITED failure modes with exactly which adds still proceed. The gaps are minor: it does not restate the destructive/irreversible framing the annotations imply, and the error-code names are asserted without saying what recovery looks like. Strong disclosure of side effects and partial-failure rules, just short of fully self-contained.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded in the first clause, which is good, but the text then runs into long parenthetical-chained sentences (especially the final rate-limit sentence) that pack several conditions into one breath. Most content earns its place, yet the density and heavy parenthetical nesting make it harder to parse than it needs to be for a five-parameter mutation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, open-world mutation, the description covers the permission model, the invite semantics, email side effects, rate limits, error codes, and partial-failure behavior. An output schema exists, and the description's brief mention of status 'invited' and inviteUrl is complementary rather than redundant.

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 the schema does not: which member forms trigger an email versus a silent membership, and the exact conditions under which note is refused (no email sent). It says nothing about the why parameter, which carries a non-obvious 'Required for workspace items' constraint, but the schema already documents that fully.

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 first sentence gives a specific verb ('Add or invite') and resource ('someone to the workspace') and immediately specifies the two possible roles, so the agent knows exactly what the call does. It even clarifies that an add of an existing member with another role doubles as a role change, but it never names workspace_member_set_role or team_add_member, so the boundary with those siblings must be inferred.

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?

Usage conditions are implied rather than stated: 'Anyone who may share here (editors, guests included) may add' gives a permission precondition, and the invite-vs-add distinction gives context, but there is no explicit 'use X instead when Y'. The note that adding an existing member with another role changes it effectively overlaps workspace_member_set_role without routing the agent between the two.

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

All Tokenrip 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.