Skip to main content
Glama

Vee3

by io.github.Vee3io

clerk.update_instance_organization_settings

Update organization feature settings for a connected Clerk instance.

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 updated organization settings.

Cost = 8 tokens.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
enabledNoWhether organizations should be enabled for the instance.
creator_roleNoDefault role assigned to the organization creator.
domains_enabledNoWhether organization domains should be enabled.
clerk_instance_idNoClerk instance id (ins_...) from clerk.get_connected_accounts. Omit to use the default connected account.
admin_delete_enabledNoWhether organization admins can delete their organization.
domains_default_roleNoDefault role for members who join via a verified organization domain.
initial_role_set_keyNoInitial role set key applied to new organizations.
max_allowed_membershipsNoMaximum organization memberships allowed per user.
domains_enrollment_modesNoAllowed organization domain enrollment modes: manual_invitation, automatic_invitation, or automatic_suggestion.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
organization_settingsNoUpdated Clerk instance organization settings from the Backend API.

Schema Changelog

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

  1. Added

TDQS

A3.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It implies a mutation but does not disclose issues like partial update semantics (what happens to omitted fields), permission requirements, reversibility, or side effects. It only mentions returning updated settings and token cost, which is insufficient behavioral transparency.

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 three concise sentences plus a cost note, with the main purpose front-loaded. Every sentence provides necessary information without fluff or repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has 9 optional parameters and no required ones, making the behavior on omitted fields important. The output schema exists, so return handling is covered, but the description does not explain whether null/omitted fields mean 'leave unchanged' or 'set to null'. Adequate but with a clear gap in partial-update semantics.

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 all parameters are already described in the schema. The description adds the prerequisite call and targeting guidance, but this overlaps with the schema's description for clerk_instance_id. No significant additional parameter semantics beyond the baseline.

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 tool's purpose: 'Update organization feature settings for a connected Clerk instance.' This uses a specific verb ('update') and resource ('organization feature settings'), and distinguishes it from sibling tools like update_instance_settings or update_instance_communication_settings.

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 gives explicit usage context: 'Call clerk.get_connected_accounts first' and explains how to target a specific connection with clerk_instance_id or use the default. However, it does not state when not to use the tool or mention alternatives, so it stops short of full 5.

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

All Vee3 toolsInspect
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.

Resources