Page Lemon

Add people

add_people

Destructive

Gives people access, or sets a workspace person's role (Owner or Admin). developer (workspace: a seat), viewer, admin, custom+group, member (users). Returns approve_url.

Input Schema

Name	Required	Description
`role`	No	developer, viewer, member, admin or custom. An audience (students, clients) is member
`site`	Yes
`group`	No
`emails`	No	Emails; for member also company domains (required unless confirm_token)
`notify`	No	member: email each new address (default true)
`permissions`	No	Ticks, personal site
`confirm_token`	No

Output Schema

Name	Required	Description	Default
`approve_url`	No
`agent_message`	No
`confirm_token`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 27, 2026
- addedOutput schema / properties / agent_message
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / approve_url
```
Added value: +{
+  "type": "string"
+}
```
Changed1 schema field changedOct 27, 2026
- removedInput schema / properties / confirm_token / description
```
Removed value: -"From the first call (site only): approval status"
```

Changed1 schema field changedOct 25, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "confirm_token": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

Changed7 schema fields changedOct 22, 2026

changedInput schema / properties / emails / description

Previous value: -"Email addresses; for visitor also company domains, e.g. acme.com (required unless confirm_token)"New value: +"Emails; for member also company domains (required unless confirm_token)"

addedInput schema / properties / group
```
Added value: +{
+  "type": "string"
+}
```

changedInput schema / properties / permissions / description

Previous value: -"collaborator: exactly these ticks; for existing collaborators, changes theirs"New value: +"Ticks, personal site"

removedInput schema / properties / permissions / items / enum

Removed value: -[
-  "edit_site",
-  "members_view",
-  "members_edit",
-  "ai_key",
-  "scan"
-]

changedInput schema / properties / role / description

Previous value: -"Required unless confirm_token. An audience (students, clients) is member. viewer also sees versions and people"New value: +"developer, viewer, member, admin or custom. An audience (students, clients) is member"

removedInput schema / properties / role / enum

Removed value: -[
-  "editor",
-  "collaborator",
-  "viewer",
-  "visitor",
-  "member",
-  "workspace_visitor",
-  "workspace_viewer"
-]

removedInput schema / properties / site / description
```
Removed value: -"Site name"
```

Changed6 schema fields changedOct 21, 2026

changedInput schema / properties / confirm_token / description

Previous value: -"From the first call: re-call with it (site only) for the approval status"New value: +"From the first call (site only): approval status"

removedInput schema / properties / emails / maxItems
```
Removed value: -50
```

addedInput schema / properties / permissions

Added value: +{
+  "description": "collaborator: exactly these ticks; for existing collaborators, changes theirs",
+  "items": {
+    "enum": [
+      "edit_site",
+      "members_view",
+      "members_edit",
+      "ai_key",
+      "scan"
+    ],
+    "type": "string"
+  },
+  "type": "array"
+}

changedInput schema / properties / role / description

Previous value: -"Required unless confirm_token. collaborator (old name editor): a Site Collaborator, edits. An audience (students, clients) is member (old name visitor; a Site Member): sees only the invite-only site. viewer: a Site Viewer, also sees versions and people. workspace_viewer (old name workspace_visitor): a Workspace Viewer, views every site of the workspace in the app, read-only"New value: +"Required unless confirm_token. An audience (students, clients) is member. viewer also sees versions and people"

changedInput schema / properties / site / description

Previous value: -"Site name, e.g. brave-otter-4821"New value: +"Site name"

changedOutput schema / (root)

Previous value: -{
-  "additionalProperties": {},
-  "properties": {
-    "agent_message": {
-      "type": "string"
-    },
-    "confirm_token": {
-      "type": "string"
-    },
-    "error": {
-      "description": "On failure (isError): {code, message}"
-    }
-  },
-  "type": "object"
-}New value: +null

Changed3 schema fields changedOct 21, 2026

changedInput schema / properties / notify / description

Previous value: -"visitor: email each new address (default true)"New value: +"member: email each new address (default true)"

changedInput schema / properties / role / description

Previous value: -"Required unless confirm_token. An audience (students, clients) is visitor (an invited visitor): sees only the invite-only site. viewer is a collaborator: also sees versions and people. workspace_visitor: views every site of the workspace in the app, read-only"New value: +"Required unless confirm_token. collaborator (old name editor): a Site Collaborator, edits. An audience (students, clients) is member (old name visitor; a Site Member): sees only the invite-only site. viewer: a Site Viewer, also sees versions and people. workspace_viewer (old name workspace_visitor): a Workspace Viewer, views every site of the workspace in the app, read-only"

changedInput schema / properties / role / enum

Previous value: -[
-  "editor",
-  "viewer",
-  "visitor",
-  "workspace_visitor"
-]New value: +[
+  "editor",
+  "collaborator",
+  "viewer",
+  "visitor",
+  "member",
+  "workspace_visitor",
+  "workspace_viewer"
+]

Changed2 schema fields changedOct 20, 2026

changedInput schema / properties / role / description

Previous value: -"Required unless confirm_token. An audience (students, clients) is visitor (an invited visitor): sees only the invite-only site. viewer is a collaborator: also sees versions and people"New value: +"Required unless confirm_token. An audience (students, clients) is visitor (an invited visitor): sees only the invite-only site. viewer is a collaborator: also sees versions and people. workspace_visitor: views every site of the workspace in the app, read-only"

changedInput schema / properties / role / enum

Previous value: -[
-  "editor",
-  "viewer",
-  "visitor"
-]New value: +[
+  "editor",
+  "viewer",
+  "visitor",
+  "workspace_visitor"
+]

Changed1 schema field changedOct 15, 2026

changedInput schema / properties / role / description

Previous value: -"Required unless confirm_token. An audience (students, clients) is visitor: sees only the members-only site. viewer is a collaborator: also sees versions and people"New value: +"Required unless confirm_token. An audience (students, clients) is visitor (an invited visitor): sees only the invite-only site. viewer is a collaborator: also sees versions and people"

Changed1 schema field changedOct 15, 2026

changedInput schema / properties / role / description

Previous value: -"Required unless confirm_token"New value: +"Required unless confirm_token. An audience (students, clients) is visitor: sees only the members-only site. viewer is a collaborator: also sees versions and people"

First observedOct 14, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already disclose that this is a destructive, non-idempotent, open-world mutation. The description adds some role context and mentions returning approve_url, but it does not explain approval flow, notification behavior, or what access changes entail beyond the annotations.

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?

The description is a single front-loaded sentence with no filler. However, the role list is dense and somewhat cryptic, especially 'developer (workspace: a seat)' and 'custom+group'.

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 access-granting tool with seven parameters, the description is minimally adequate. It covers the core purpose and role values, but omits key usage distinctions and parameter details, even though the output schema covers return values.

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 57%, so the description must help with the undocumented parameters. It clarifies role values such as developer, viewer, admin, custom+group, and member, but leaves site, group, emails, notify, permissions, and confirm_token largely unexplained.

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 states a specific verb and resource: giving people access or setting a workspace person's role. It is clear what the tool does, but it does not explicitly differentiate itself from sibling tools such as invite_users or remove_people.

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 phrase 'Gives people access, or sets a workspace person's role' implies the usage context, but there is no explicit when-to-use guidance, no exclusions, and no comparison to alternatives like invite_users.

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

All Page Lemon tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?