Skip to main content
Glama

Vee3

by io.github.Vee3io

clerk.update_instance_settings

Update core settings for a connected Clerk application 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 instance settings.

Cost = 8 tokens.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hibpNoWhether Have I Been Pwned password checking should be enabled.
test_modeNoWhether the instance should run in test mode.
support_emailNoSupport email address shown to end users.
allowed_originsNoAllowed browser origins for the instance.
clerk_js_versionNoPinned Clerk.js version for the instance.
clerk_instance_idNoClerk instance id (ins_...) from clerk.get_connected_accounts. Omit to use the default connected account.
development_originNoDevelopment origin URL for local testing.
url_based_session_syncingNoWhether URL-based session syncing should be enabled.
preferred_sign_in_strategy_when_password_requiredNoPreferred sign-in strategy when a password is required: "password" or "otp".

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
instance_settingsNoUpdated Clerk instance settings from the Backend API.

Schema Changelog

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

  1. Added

TDQS

A4/5.0
Behavior3/5

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

With no annotations, description carries the burden. It discloses mutation ('Update'), return value ('Returns the updated instance settings'), and cost (8 tokens). Missing behavioral details like permissions, partial vs full replacement of settings, or error handling.

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?

Five short, purposeful sentences: purpose, prerequisite, targeting, return value, cost. Front-loaded and free of fluff.

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 a 9-parameter update tool with an output schema, it covers prerequisite and instance selection, which are the most non-obvious aspects. Missing clarification on whether omitted parameters are left unchanged or reset, but overall adequate.

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 baseline is 3. The description adds context for clerk_instance_id ('omit to use default') but does not enrich other parameter semantics beyond schema.

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 updates core settings for a connected Clerk instance, using a specific verb and resource. It distinguishes from sibling update_instance_* tools by scoping to 'core settings' rather than communication, OAuth, organization, or restrictions.

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?

It gives explicit prerequisite guidance (call clerk.get_connected_accounts first) and explains how to target a connection via clerk_instance_id or default. However, it does not explicitly contrast with alternative update_instance_* tools or state when not to use this tool.

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