Skip to main content
Glama

Send Team Invite Email

sendTeamInviteEmail

Email an invitation to its recipient. Use this to deliver an invitation created by createTeamInvite (which never sends mail on its own), or to resend one the recipient never received. The accept link is always built from the server-configured app origin.

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": {
      "id": "<id>"
    },
    "name": "sendTeamInviteEmail"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesID of the invitation to email.
team_idNoDuvo team UUID to operate on. API keys are pinned to a single team — omit this (it falls back to the key's team) or pass that same team; a different team is rejected. OAuth callers, who can span multiple teams, should pass the target team here.
scheduleNoOptional time for the interview. The invitation email then carries a calendar invite for it, the interview link stays valid until a week after it, and a later send with a new time moves the same calendar event. At most 90 days ahead. Only available while calendar invites are on for the team.
frontendUrlNoDeprecated. Accepted for backward compatibility and IGNORED: the accept link is always built from the server-configured app origin, so a caller cannot point invitation emails at another host.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / schedule
      Added value: +{
      +  "description": "Optional time for the interview. The invitation email then carries a calendar invite for it, the interview link stays valid until a week after it, and a later send with a new time moves the same calendar event. At most 90 days ahead. Only available while calendar invites are on for the team.",
      +  "properties": {
      +    "durationMinutes": {
      +      "description": "How long the interview is booked for, 15 to 240 minutes.",
      +      "maximum": 240,
      +      "minimum": 15,
      +      "type": "integer"
      +    },
      +    "startAt": {
      +      "description": "When the interview starts, as an ISO 8601 date-time with an offset or Z, e.g. 2026-10-28T10:00:00+01:00. Must be in the future and at most 90 days ahead.",
      +      "format": "date-time",
      +      "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z|([+-](?:[01]\\d|2[0-3]):[0-5]\\d)))$",
      +      "type": "string"
      +    },
      +    "timeZone": {
      +      "description": "IANA time zone the time is shown in, e.g. Europe/Prague. The calendar shows it in each reader's own zone.",
      +      "maxLength": 64,
      +      "minLength": 1,
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "startAt",
      +    "durationMinutes",
      +    "timeZone"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already establish that this is a non-read-only, open-world operation. The description adds important context beyond them: createTeamInvite never sends mail, resends are allowed, the accept link is server-origin, and frontendUrl is ignored. It does not cover delivery failure behavior, rate limits, or idempotency beyond the annotation.

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?

Three tight sentences with the action front-loaded and no wasted wording. Each sentence contributes distinct information about purpose, usage, or implementation behavior.

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 an email-sending tool with a nested schedule object and no output schema, the description covers the critical non-schema behavior: the creator/sender split, resend semantics, and fixed accept-link origin. Remaining omissions such as return shape or failure behavior are less central given the rich schema and annotations.

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 coverage is 100%, and the schema itself documents id, team_id, the nested schedule object, and the deprecated frontendUrl. The description reinforces the frontendUrl origin behavior but adds little parameter-level meaning beyond what the schema already provides.

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 the specific action clearly: 'Email an invitation to its recipient.' It also explicitly relates the tool to createTeamInvite, making the sender/creator distinction 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?

Gives two concrete use cases: delivering an invitation created by createTeamInvite and resending one the recipient never received. It does not explicitly say when not to use it or name other alternatives such as bulkCreateTeamInvites, so it falls short of full when/when-not guidance.

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