Vee3

clerk.get_sign_up

Retrieve an in-progress sign-up from a connected Clerk application by sign-up id.

Call clerk.get_connected_accounts first. Pass clerk_instance_id to target a specific connection, or omit it to use the default account.

Returns status, contact fields, missing and unverified fields, and completion timestamps.

Cost = 3 tokens.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`sign_up_id`	Yes	Clerk sign-up id (su_...) to retrieve.
`clerk_instance_id`	No	Clerk instance id (ins_...) from clerk.get_connected_accounts. Omit to use the default connected account.

Output Schema

TableJSON Schema

Name	Required	Description
`id`	No	Clerk sign-up id (su_...).
`status`	No	Sign-up status: "missing_requirements", "complete", or "abandoned".
`username`	No	Username associated with the in-progress sign-up.
`last_name`	No	Last name collected during sign-up.
`abandon_at`	No	Unix timestamp in milliseconds when the sign-up will be abandoned.
`first_name`	No	First name collected during sign-up.
`phone_number`	No	Phone number associated with the in-progress sign-up.
`email_address`	No	Email address associated with the in-progress sign-up.
`missing_fields`	No	Fields still required before the sign-up can complete.
`created_user_id`	No	Clerk user id created when the sign-up completed.
`unverified_fields`	No	Fields that still need verification.
`created_session_id`	No	Clerk session id created when the sign-up completed.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed1 schema field changedJul 31, 2026

changedInput schema / properties / sign_up_id / description

Previous value: -"Clerk sign-up id (su_...) to retrieve or update."New value: +"Clerk sign-up id (su_...) to retrieve."

AddedJul 13, 2026

TDQS

A4.5/5.0

Behavior4/5

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

With no annotations, the description carries the full burden. It discloses return contents (status, contact fields, missing/unverified fields, completion timestamps) and a non-standard cost of 3 tokens. It also implies read-only behavior through 'Retrieve.' Not exhaustive (e.g., no error behavior), but strong for a simple getter.

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?

Four sentences, each serving a purpose: purpose (sentence 1), prerequisite (sentence 2), instance parameter guidance (sentence 3), return summary and cost (sentence 4). Front-loaded, no filler, perfectly sized for the tool's simplicity.

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?

The tool is simple (2 params, 1 required) and has an output schema covering return values. The description supplies all operational context needed: prerequisites, instance selection, returned fields, and cost. There are no gaps in usage understanding.

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 description coverage is 100%, so the baseline is 3. The description adds meaningful context for clerk_instance_id by explaining how to use it (target a specific connection vs. default) and references the prerequisite function. This goes beyond the schema's bare parameter descriptions.

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 ('Retrieve') and the specific resource ('an in-progress sign-up') by ID. It scopes to 'a connected Clerk application' and distinguishes itself from sibling tools like get_session or get_user by focusing on sign-ups.

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?

Provides a clear prerequisite ('Call clerk.get_connected_accounts first') and explains how to target a specific connection via clerk_instance_id or default behavior. However, it does not explicitly state when not to use this tool or name alternative tools for non-sign-up scenarios, 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.

All Vee3 tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.