Vee3

clerk.create_enterprise_connection

Create a SAML or OIDC enterprise SSO connection in a connected Clerk application.

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

Returns the new enterprise_connection summary.

Cost = 10 tokens.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	Yes	Display name for the enterprise connection.
`oidc`	No	OIDC client configuration when provider uses OAuth.
`saml`	No	SAML IdP configuration when provider uses SAML.
`active`	No	Whether the connection is active.
`domains`	Yes	Email domains that may use this connection.
`provider`	Yes	Identity provider key (for example saml_custom or oidc_custom).
`organization_id`	No	Clerk organization id (org_...) to link to this connection.
`clerk_instance_id`	No	Clerk instance id (ins_...) from clerk.get_connected_accounts. Omit to use the default connected account.
`custom_attributes`	No	Custom attribute mappings from the IdP to user metadata.
`sync_user_attributes`	No	Whether to sync user attributes on each sign-in.
`allow_organization_account_linking`	No	Whether account linking via organization membership is allowed.
`disable_additional_identifications`	No	Whether to block additional identifications for this connection.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`enterprise_connection`	No	Newly created enterprise SSO connection.

Schema Changelog

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

AddedJul 13, 2026

TDQS

A4/5.0

Behavior3/5

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

With no annotations, the description carries the burden. It discloses the return value ('Returns the new enterprise_connection summary'), the cost, and the prerequisite of a connected application. It does not discuss permissions, side effects beyond creation, or behavior differences between SAML and OIDC providers, making it minimally adequate.

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?

The description is compact: a purpose sentence, a usage sentence, a return sentence, and a cost line. No wasted words, and the most important info is front-loaded.

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?

Despite the 12-parameter schema, the description covers the essential usage flow (prerequisite, target selection) and return summary. The output schema handles return details, and parameter schema handles parameter docs. It lacks explicit alternative tool guidance, but overall it is sufficiently complete for an agent to invoke it correctly for the primary use case.

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?

The input schema covers all 12 parameters with descriptions (100% coverage), so the baseline is 3. The description adds no extra parameter semantics beyond what the schema already provides; even the clerk_instance_id note is redundant with the schema text.

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 a specific action ('Create a SAML or OIDC enterprise SSO connection') with a target resource ('in a connected Clerk application'). This distinguishes it from related tools like update_enterprise_connection or test_run. The verb and resource are 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?

The description provides clear contextual guidance: call clerk.get_connected_accounts first and optionally pass clerk_instance_id, with a fallback to the default account. However, it does not explicitly compare to alternative tools (e.g., test_run, list, update), so it falls short of explicit 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.

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.

TDQS

A4.1/5.0

Disambiguation5/5

Each tool has a distinct purpose, further clarified by group prefixes and clear descriptions. Within each group, tools perform different operations (e.g., domains.lookup vs. domains.whois vs. domains.rdap) with no ambiguity.

Naming Consistency5/5

All tools follow a consistent group.tool_name pattern using snake_case. The naming is predictable and uniformly applied across all groups.

Tool Count4/5

78 tools is high, but the server aggregates multiple distinct API domains (11 groups). Each group has a reasonable number of tools, typically under 10, with TikTok having 17. The count reflects breadth, not bloat.

Completeness5/5

Each domain's tool set covers the primary expected operations (e.g., search, details, reviews, metrics, user info). There are no obvious gaps for read-only analytical use; features like posting are likely out of scope.

clerk.create_enterprise_connection

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

TDQS

Resources