Skip to main content
Glama

Vee3

by io.github.Vee3io
OverviewAdmin

clerk.list_organization_domains

List organization domains across a Clerk instance. Optionally filter to one organization via organization_id.

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

Returns domain summaries and total_count.

Cost = 5 tokens.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of results to return (1–500).
queryNoSearch domains by name or organization id. Values starting with org_ match organization id exactly; otherwise performs a case-insensitive partial match on the domain name.
offsetNoNumber of results to skip before returning.
verifiedNoFilter by verification status: "true" or "false".
enrollment_modeNoFilter or set enrollment mode: manual_invitation, automatic_invitation, or automatic_suggestion.
organization_idNoFilter domains to a specific Clerk organization id (org_...).
clerk_instance_idNoClerk instance id (ins_...) from clerk.get_connected_accounts. Omit to use the default connected account.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainsNoOrganization domains returned for the requested page.
total_countNoTotal number of domains matching the filter.

Schema Changelog

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

  1. Changed6 schema fields changed
    • addedInput schema / properties / organization_id / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedInput schema / properties / organization_id / default
      Added value: +null
    • changedInput schema / properties / organization_id / description
      Previous value: -"Clerk organization id (org_...) to operate on."New value: +"Filter domains to a specific Clerk organization id (org_...)."
    • removedInput schema / properties / organization_id / type
      Removed value: -"string"
    • addedInput schema / properties / query
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Search domains by name or organization id. Values starting with org_ match organization id exactly; otherwise performs a case-insensitive partial match on the domain name.",
+  "title": "Query"
+}
    • removedInput schema / required
      Removed value: -[
-  "organization_id"
-]
  2. Added

TDQS

A4.4/5.0
Behavior4/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 format ('domain summaries and total_count'), mentions a prerequisite, and states a token cost. It doesn't explicitly state read-only behavior or rate limits, but 'list' implies read-only and the disclosed cost adds behavioral context.

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 sentences plus a cost note, front-loaded with the purpose, and contains no filler. Each sentence adds distinct value: purpose, prerequisite/usage, and return/cost.

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 output schema exists and all parameters are described in the schema, the description covers the key non-schema aspects: prerequisite, optional filtering, and return summary. Minor gaps like error handling or sorting behavior are not critical for a straightforward list operation.

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?

The schema already provides 100% parameter description coverage. The description adds contextual meaning for clerk_instance_id by explaining its relationship to get_connected_accounts and the default-account fallback, which is valuable beyond the 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 identifies the action ('List') and resource ('organization domains'), specifying scope ('across a Clerk instance') and an optional filter ('via organization_id'). This distinguishes it from sibling tools like list_domains or list_organizations by the specific resource type.

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 explicitly instructs to call clerk.get_connected_accounts first and explains how to use clerk_instance_id to target a specific connection or use the default. This provides clear usage context, though it doesn't explicitly discuss when to prefer this over related list tools.

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.

Resources