Skip to main content
Glama

resend_user_invite

Resend a pending user invite email for an invite that has not been accepted. Sends a fresh email without altering the invite details.

Instructions

Resend the email for a pending invite that has not been accepted, unlike invite_user which creates a new invite. This sends a fresh email without modifying the invite record, expiry, or role; use get_user_invite first if you are unsure whether the invite still exists and list_user_invites to discover invite_ids.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
invite_idYesThe invite ID to resend

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYesWhether the tool call succeeded and returned structured data
dataNoStructured success payload when ok is true
errorNoStructured error payload when ok is false

Implementation Reference

  • The MCP tool handler for 'resend_user_invite'. It registers the tool with the MCP server, uses the schema for input validation (invite_id), calls service.users.resendUserInvite(params.invite_id), and returns a success message.
    // Phase 1: Resend user invite tool
    server.tool(
    	"resend_user_invite",
    	"Resend the email for a pending invite that has not been accepted, unlike invite_user which creates a new invite. This sends a fresh email without modifying the invite record, expiry, or role; use get_user_invite first if you are unsure whether the invite still exists and list_user_invites to discover invite_ids.",
    	USERS_TOOL_SCHEMAS.resendUserInvite,
    	async (params) => {
    		await service.users.resendUserInvite(params.invite_id);
    		return {
    			content: [
    				{
    					type: "text",
    					text: JSON.stringify(
    						{
    							message: `Successfully resent invite ${params.invite_id}`,
    							success: true,
    						},
    						null,
    						2,
    					),
    				},
    			],
    		};
    	},
    );
  • The Zod schema for the resendUserInvite tool, defining the 'invite_id' input parameter as a required string.
    resendUserInvite: {
    	invite_id: z.string().describe("The invite ID to resend"),
    },
  • The tool is registered via server.tool('resend_user_invite', ...) inside the registerUsersTools function.
    // Phase 1: Resend user invite tool
    server.tool(
    	"resend_user_invite",
    	"Resend the email for a pending invite that has not been accepted, unlike invite_user which creates a new invite. This sends a fresh email without modifying the invite record, expiry, or role; use get_user_invite first if you are unsure whether the invite still exists and list_user_invites to discover invite_ids.",
    	USERS_TOOL_SCHEMAS.resendUserInvite,
    	async (params) => {
    		await service.users.resendUserInvite(params.invite_id);
    		return {
    			content: [
    				{
    					type: "text",
    					text: JSON.stringify(
    						{
    							message: `Successfully resent invite ${params.invite_id}`,
    							success: true,
    						},
    						null,
    						2,
    					),
    				},
    			],
    		};
    	},
    );
  • The service method resendUserInvite that performs the actual HTTP POST to /admin/users/invites/{inviteId}/resend on the Portkey API.
    async resendUserInvite(inviteId: string): Promise<{ success: boolean }> {
    	await this.post(
    		`/admin/users/invites/${this.encodePathSegment(inviteId)}/resend`,
    	);
    	return { success: true };
    }
Behavior5/5

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

The description clarifies that the tool 'sends a fresh email without modifying the invite record, expiry, or role', which complements the annotations (readOnlyHint=false, destructiveHint=false) by specifying the non-destructive nature despite being a mutation. No contradiction with annotations.

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?

Two concise sentences that efficiently deliver purpose, behavior, usage differentiation, and prerequisite tool recommendations without any redundant information.

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?

Given the simple parameter set and comprehensive annotations, the description provides complete context including behavior, side effects (none), and usage hints. No gaps remain for an agent to safely invoke the tool.

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% (single parameter invite_id with clear description). The tool description does not add further semantic meaning beyond what the schema already provides for the parameter, thus baseline score of 3 is appropriate.

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 action ('Resend the email for a pending invite that has not been accepted') and contrasts with sibling tool 'invite_user' which creates a new invite, making the purpose and 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 Guidelines5/5

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

Explicitly states when to use this tool (for resending pending invites) and when not (use invite_user to create new invites). Additionally, recommends calling get_user_invite first to verify invite existence and list_user_invites to discover IDs, providing excellent usage context.

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/s-b-e-n-s-o-n/portkey-admin-mcp'

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