Skip to main content
Glama

Send Invitation

send_invitation

Invite someone by email to the organization and to one or more of its workspaces, each with a role. AdaptlyPost emails the invitation, which lasts 7 days; on accepting, the person joins with organizationRole and each listed workspace with its role. Confirm the email, workspaces and roles with the user first. Needs the members.manage permission, which Admin holds. A member who is not an organization owner or admin may only invite org-member, only to workspaces where they hold members.manage, and only with a role no higher than their own there; only the owner may invite an org-admin, and only an organization owner or admin may set creditAllowance. Otherwise it fails with 403 permission_denied. Fails with 403 subscription_required when the plan has no team seat left: tell the user to upgrade and do not retry. Fails with 400 when the person is already a member or already invited.

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": {
      "email": "<email>",
      "workspaces": "<workspaces>"
    },
    "name": "send_invitation"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailYesEmail address to invite
workspacesYesWorkspaces the person joins on accepting, at least one, each with its role
workspaceIdNoWorkspace to act in: an id from list_workspaces. Omit to act in the workspace list_workspaces marks current. Use the same workspaceId for every call about the same workspace, since ids from one workspace (accounts, posts, uploads) do not exist in another
creditAllowanceNoAI credits the member may spend from the owner's pool: { mode: "MONTHLY", monthlyAmount } or { mode: "FIXED", balance }. Leave out for none. Only an organization owner or admin may set it
organizationRoleNoRole in the organization: org-member (the default) or org-admin. Only the organization owner may invite an org-admin

Output Schema

NameRequiredDescriptionDefault
resultYesThe invitation: id, email, organizationId, organizationRole, status (pending, accepted, expired or revoked), workspaces [{ workspaceId, workspaceName, role }], expiresAt and createdAt.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only say this is a non-read-only, non-idempotent, non-destructive open-world call; the description adds substantially more: invitations expire after 7 days, acceptance grants organizationRole and per-workspace roles, and three distinct error outcomes (403 permission_denied, 403 subscription_required, 400 already-member/already-invited) with retry guidance.

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 core action and pre-confirmation instruction are front-loaded, and no sentence is filler. The authorization sentence is a long, semicolon-chained run-on that an agent must parse carefully, which costs a point on structure rather than on length.

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 5-parameter mutation with an output schema already covering return values, the description covers everything an agent needs to call it correctly: permissions, role escalation limits, creditAllowance authority, expiry, and terminal error handling. Nothing material is left to inference.

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, and coverage of the five parameters is already thorough. Above that baseline, the description adds authorization semantics the schema cannot express: who may grant org-admin, who may set creditAllowance, and the ceiling that a non-admin inviter cannot exceed their own workspace role.

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 first sentence states a specific verb (invite) plus the exact resource and scope: a person, by email, into the organization and one or more workspaces with per-workspace roles. That is enough to tell it apart from revoke_invitation or send_inbox_message without opening any schema.

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

Usage Guidelines5/5

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

It states preconditions (needs members.manage, which Admin holds), a mandatory pre-step (confirm email, workspaces and roles with the user first), and explicit when-not conditions via role-tier rules for non-admin members. It also tells the agent what to do on each failure mode, including 'tell the user to upgrade and do not retry' for subscription_required.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources