HeyLead

Overview Schema Source Related Servers Discussions Admin

organization

Destructive

Switch between client workspaces, list organizations, invite or remove members, and create new ones while staying signed in. Manage roles and access across teams.

Instructions

List, switch, or manage hosted HeyLead organizations.

Use this to work across client workspaces. The person stays signed in;
only the active organization changes.

Args:
    action: list | switch | members | invite | remove_member | create
    org_id: Organization id (required for switch; optional if already switched).
    email: Invitee email (invite), or the new org name (create).
    role: editor or viewer (invite).
    user_id: Member to remove (remove_member).

Input Schema

TableJSON Schema

Name	Required	Default
`role`	No	editor
`email`	No
`action`	No	list
`org_id`	No
`user_id`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.10.375Sep 18, 2026

TDQS

A4.1/5.0

Behavior3/5

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

The annotations already indicate readOnlyHint=false and destructiveHint=true; the description adds one useful behavioral fact (switching organizations does not sign the user out). However, it does not explain consequences of destructive actions such as remove_member, and it omits details about what gets deleted or changed beyond the action names.

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 compact and front-loaded with the purpose, followed by a short usage context and an Args list. Every line conveys a distinct fact with no filler, making it easy for an agent to parse quickly.

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 polymorphic tool with 5 parameters and 0% schema coverage, the description covers all actions and parameter semantics, and there is an output schema to handle return values. It is slightly ambiguous about which parameters are ignored for each action and what the 'members' action requires, but it is otherwise sufficiently complete.

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?

Schema coverage is 0%, and the description fully compensates: the Args block explains each parameter's role, valid action values, and conditional requirements (org_id required for switch, email doubles as invitee email or new org name, role is editor/viewer, user_id is for remove_member). This gives an agent everything needed to assemble a correct call.

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 opens with specific actions ('List, switch, or manage hosted HeyLead organizations') and an explicit action list, so an agent can identify the resource and main operations. It does not explicitly contrast itself with sibling tools like account or contacts, and 'manage' is broad, so it is clear but not a 5.

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?

It explains when to use the tool: 'Use this to work across client workspaces' and clarifies that the person stays signed in while the active organization changes. It does not mention alternative tools or exclusion conditions, so it stops 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.