Skip to main content
Glama

Vee3

by io.github.Vee3io

clerk.update_api_key

Update an API key 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 updated API key summary.

Cost = 8 tokens.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
claimsNoUpdated custom claims for tokens minted from this API key.
scopesNoUpdated permission scopes for the API key.
subjectNoUpdated subject (user_... or org_...).
api_key_idYesClerk API key id (ak_...) to retrieve, update, delete, or revoke.
descriptionNoUpdated description for the API key.
clerk_instance_idNoClerk instance id (ins_...) from clerk.get_connected_accounts. Omit to use the default connected account.
seconds_until_expirationNoUpdated seconds until expiration from now.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
api_keyNoUpdated Clerk API key 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?

No annotations are provided, so the description must carry behavioral info. It discloses the return behavior ('Returns the updated API key summary') and the token cost, but does not describe side effects, permission requirements, or how omitted fields are handled. This is adequate but not rich, hence a 3.

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—three short paragraphs plus a cost line—and front-loads the main purpose. Every sentence adds value, with no fluff. Score 5.

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?

The tool has 7 params and an output schema, so return details are covered. The description covers essential setup (get_connected_accounts) and connection selection. It omits edge cases like overwrite behavior, but given the schema's thoroughness, it is reasonably complete. Score 4.

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%, so the baseline is 3. The description reinforces clerk_instance_id semantics, but mostly restates the schema's existing description. No additional parameter details are provided, so it stays at 3.

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 opens with 'Update an API key in a connected Clerk application,' clearly stating the verb and resource. This distinguishes it from sibling tools like create_api_key, revoke_api_key, and delete_api_key.

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 provides a clear prerequisite: 'Call clerk.get_connected_accounts first.' It also explains how to choose a connection via clerk_instance_id or default. However, it does not explicitly state when not to use this tool or name alternatives, so it is a 4 rather than 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 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