Skip to main content
Glama

Vee3

by io.github.Vee3io

clerk.update_organization_role

Update an organization role 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 role summary.

Cost = 8 tokens.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoUpdated role display name.
role_idYesClerk organization role id to retrieve, update, or delete.
descriptionNoUpdated role description.
permissionsNoPermission keys to assign to the role.
clerk_instance_idNoClerk instance id (ins_...) from clerk.get_connected_accounts. Omit to use the default connected account.
is_creator_eligibleNoWhether this role may be assigned as organization creator.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
organization_roleNoUpdated organization role summary.

Schema Changelog

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

  1. Changed1 schema field changed
    • changedInput schema / properties / role_id / description
      Previous value: -"Clerk organization role id to retrieve, update, delete, or assign permissions to."New value: +"Clerk organization role id to retrieve, update, or delete."
  2. Added

TDQS

A4.2/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 for behavioral disclosure. It mentions prerequisite steps, the return value ('Returns the updated role summary'), and cost, but does not disclose permission requirements, irreversibility, or how unspecified fields are treated during update.

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 and well-structured: operation statement, prerequisite, return value, and cost. Every sentence earns its place without redundancy.

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?

Given the tool's moderate complexity, 100% schema parameter coverage, and presence of an output schema, the description adequately covers connection targeting, prerequisites, return value, and cost. It does not discuss edge effects or alternatives, but overall is sufficient for selection and invocation.

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 coverage is 100%, so baseline is 3. The description adds meaningful guidance for clerk_instance_id ('Pass clerk_instance_id to target a specific connection, or omit it to use the default account'), going beyond the schema. Other parameters rely on their schema 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 ('Update an organization role') and the resource ('in a connected Clerk application'). It is specific enough to distinguish itself from sibling tools like update_organization or update_organization_permission.

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 explicit prerequisite guidance: 'Call clerk.get_connected_accounts first' and explains how to target a specific connection versus using the default account with clerk_instance_id. It lacks explicit when-not-to-use or alternative tool comparisons, but offers clear contextual usage.

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