Skip to main content
Glama

List application domains

list_domains
Read-onlyIdempotent

List the domains of an application's production instance, so the application needs one first (see create_production_instance). Returns data, where each domain has its id, name, frontend_api_url, and the DNS records it needs (dns_targets), and total_count.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "application_id": "<application_id>"
    },
    "name": "list_domains"
  }
}

Input Schema

NameRequiredDescriptionDefault
application_idYesClerk application ID (app_…).

Output Schema

NameRequiredDescriptionDefault
dataYes
total_countYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "https://json-schema.org/draft/2020-12/schema",
      +  "additionalProperties": {},
      +  "properties": {
      +    "data": {
      +      "items": {
      +        "additionalProperties": {},
      +        "properties": {
      +          "dns_targets": {
      +            "items": {
      +              "additionalProperties": {},
      +              "properties": {
      +                "host": {
      +                  "type": "string"
      +                },
      +                "record_type": {
      +                  "type": "string"
      +                },
      +                "required": {
      +                  "type": "boolean"
      +                },
      +                "value": {
      +                  "type": "string"
      +                }
      +              },
      +              "required": [
      +                "record_type",
      +                "host",
      +                "value",
      +                "required"
      +              ],
      +              "type": "object"
      +            },
      +            "type": "array"
      +          },
      +          "frontend_api_url": {
      +            "type": "string"
      +          },
      +          "id": {
      +            "type": "string"
      +          },
      +          "name": {
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "id",
      +          "name",
      +          "frontend_api_url"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "total_count": {
      +      "type": "number"
      +    }
      +  },
      +  "required": [
      +    "data",
      +    "total_count"
      +  ],
      +  "type": "object"
      +}
  2. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered structurally. The description adds the prerequisite dependency on a production instance existing, which is behavioral context not present in the annotations. It adds nothing about pagination or ordering of the list, which would have pushed this higher.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One compact sentence front-loads the action and scope, then covers the prerequisite and the return shape. The clause 'so the application needs one first' is slightly awkward phrasing but carries real information. No filler.

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?

An output schema exists, so enumerating the returned fields is redundant but harmless reinforcement. The key operational fact, that a production instance must exist, is disclosed. For a single-parameter read tool with full schema coverage and annotations, this is essentially complete.

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% and the single application_id parameter is documented in the schema as a Clerk app ID. The description adds no syntax or format detail beyond that, so the schema does all the work. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource with scope: 'List the domains of an application's production instance.' The scope qualifier (production instance) is a useful distinction. It does not, however, contrast with adjacent domain tools like get_domain_status or check_domain_dns, so an agent still has to infer the boundary.

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?

Gives a clear precondition: the application needs a production instance first, with a pointer to create_production_instance. That is real usage context rather than a restatement of the name. It stops short of saying when to prefer this over check_domain_dns or get_domain_status, so no exclusions are offered.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources