Skip to main content
Glama

Invite someone to the workspace

invite_member

Send a confirmed email invitation for someone to join the workspace and view or comment on its videos; verify the exact address before calling.

Instructions

Recordful Pro only (check get_status recorder.account.plan first). Email an invitation to join the user's workspace as a member: they can then see and comment on its videos. Only the workspace owner can. It emails someone else, so confirm the exact address with the user first, then call with confirm: true. Never guess an address.

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>",
      "confirm": "<confirm>"
    },
    "name": "invite_member"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailYesThe address to invite, exactly as the user gave it.
confirmYesMust be true, and only after the user has confirmed inviting this exact address.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.2.0

TDQS

A4.5/5.0
Behavior4/5

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

Beyond the annotations, it discloses that this sends an outbound email to a third party, that it requires owner permissions, and that the plan gates availability — real behavioral context for an openWorld, non-idempotent write. It stops short of saying what happens on a duplicate invitation or whether an invitation can be revoked, which would complete the picture.

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?

Front-loads the plan gate, then the effect, then the permission constraint, then the confirmation protocol. Every sentence carries a distinct constraint and none is redundant.

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 two-parameter mutation with no output schema, the definition covers the gate, the permission, the external side effect, and the safety protocol. An agent has everything it needs to decide whether and how to call it.

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 description coverage is 100%, so both email and confirm are already documented in the schema, including the const true constraint. The description reinforces the intent ('confirm: true', 'never guess an address') but adds no new syntax or format detail beyond it, so the baseline applies.

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?

States a specific verb and resource ('Email an invitation to join the user's workspace as a member') and even the resulting capability ('they can then see and comment on its videos'). That distinguishes it cleanly from siblings like list_members, which only reads members.

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?

Gives explicit preconditions: plan must be Recordful Pro (with the exact check, get_status recorder.account.plan), and only the workspace owner may call it. It also names the sequencing requirement (confirm the address with the user first, then call with confirm: true) and an exclusion ('Never guess an address').

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