Skip to main content
Glama
vanman2024

Multilead Open API MCP Server

by vanman2024

invite_team_member

Add users to a team with configurable invitation methods. Choose to send email invitations or auto-accept members, assign roles, and set payment permissions.

Instructions

Invite a user to become a member of a specific team

The sendAnInvitationEmail flag controls how the invitation works:

  • If False (default): No email is sent and the invitation is automatically accepted

  • If True: An email invitation is sent and the user can accept or decline

Args: team_id: The ID of the team to invite the member to (required) user_id: Your user ID (required) name: The name of the user to invite (required) email: The email address of the user to invite (required) account_roles: List of role assignments with 'roleId' and 'accounts' array (required) can_manage_payment: Whether the user can manage payment settings (default: False) send_invitation_email: Whether to send an email invitation (default: False)

Returns: Invitation object with member details and status

Example: invite_team_member( team_id="1443", user_id="1451", name="John Doe", email="john@company.com", account_roles=[ { "roleId": "6eb0c288-0a17-4f6c-88a3-bb750b34d7ca", "accounts": [1028] } ], can_manage_payment=False, send_invitation_email=True )

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
team_idYes
user_idYes
nameYes
emailYes
account_rolesYes
can_manage_paymentNo
send_invitation_emailNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively explains the two invitation modes (automatic acceptance vs. email-based acceptance/decline), which is crucial behavioral context. It also mentions default values for optional parameters. However, it doesn't cover error conditions, permission requirements, or rate limits.

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 well-structured with clear sections (purpose, flag explanation, args, returns, example). The example is comprehensive but lengthy. Some redundancy exists between the flag explanation and parameter description. Overall efficient but could be more concise.

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 mutation tool with 7 parameters, 0% schema coverage, and no annotations, the description does an excellent job covering parameters and core behavior. The presence of an output schema means return values don't need explanation. However, it lacks information about error cases, authentication requirements, and system constraints.

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

Parameters5/5

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

With 0% schema description coverage, the description fully compensates by providing detailed parameter documentation. Each parameter is clearly explained with purpose, required status, and default values where applicable. The 'account_roles' parameter gets specific structural guidance with 'roleId' and 'accounts' array details.

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?

The description clearly states the specific action ('Invite a user') and resource ('to become a member of a specific team'), distinguishing it from sibling tools like 'create_team' or 'update_team_member'. The verb+resource combination is precise and unambiguous.

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?

The description provides clear context about how the invitation works with the 'sendAnInvitationEmail' flag, explaining the two modes of operation. However, it doesn't explicitly state when to use this tool versus alternatives like 'create_team' or 'update_team_member', nor does it mention prerequisites or exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/vanman2024/multilead-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server