Skip to main content
Glama
Sign In
GoLogin MCP

GoLogin MCP

Official
by gologinapp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

post_workspaces__wid__members

Add members to a workspace by specifying their emails, roles, and access permissions using GoLogin MCP. Manage team collaboration and workspace configuration efficiently.

Instructions

Add member to workspace

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": {
      "wid": "<wid>",
      "emails": "<emails>",
      "limitedAccess": "<limitedAccess>",
      "role": "<role>"
    },
    "name": "post_workspaces__wid__members"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailsYes
foldersNo
limitedAccessYes
roleYes
widYes
workspaceNameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the action without behavioral details. It doesn't disclose required permissions, whether this is idempotent, what happens on duplicate emails, error conditions, or response format. 'Add' implies mutation but lacks safety/constraint context.

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?

The description is a single, efficient phrase with zero wasted words. It's appropriately sized for a simple action and front-loads the core purpose immediately.

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

Completeness2/5

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

For a mutation tool with 6 parameters, 0% schema coverage, no annotations, and no output schema, the description is inadequate. It covers the basic purpose but lacks parameter semantics, behavioral context, usage guidelines, and expected outcomes, leaving significant gaps for agent understanding.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate but adds no parameter information. It doesn't explain what 'wid', 'emails', 'role', 'limitedAccess', 'folders', or 'workspaceName' mean or how they interact, leaving all 6 parameters semantically undocumented.

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 'Add member to workspace' clearly states the action (add) and target resource (member to workspace). It's specific enough to understand the core function, though it doesn't differentiate from sibling tools like 'patch_workspaces__wid__members__id_' which likely updates existing members.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, when not to use it, or compare it to related tools like 'post_workspaces' (create workspace) or 'delete_workspaces__wid__members__id_' (remove member).

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

Deploy Server

Other Tools

Related Tools