Skip to main content
Glama

List a domain's API clients

list_domain_clients
Read-only

Lists a domain's API clients—machine callers that exchange a client ID and secret for a short-lived OAuth 2 token—including token, JWKS, discovery URLs, limits, and signing keys, without exposing secrets.

Instructions

Lists the API clients of a domain — machine callers that exchange a client id + secret for a short-lived token (OAuth 2 client_credentials) accepted by the domain's jwt / apiKeyOrJwt endpoints — with the token URL, the JWKS and discovery URLs, the limits and the signing keys. Never a secret.

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": {
      "domainId": "<domainId>"
    },
    "name": "list_domain_clients"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainIdYesThe domain's id — from list_domains.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.53.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds genuine behavioral value beyond that: it enumerates what is returned (token URL, JWKS and discovery URLs, limits, signing keys) and guarantees "Never a secret", which is exactly the reassurance an agent needs when surfacing credential metadata.

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 dense sentence, front-loaded with verb and resource, then narrowing to definition, returned fields, and the non-secret guarantee. Every clause earns its place; it is long but not padded.

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 read-only, single-parameter list tool with no output schema, the definition covers what the resource is, what comes back, and the security boundary. Only the routing to sibling tools is missing, which keeps it short of a 5.

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% with a single required integer domainId whose schema description already points to list_domains. The prose adds no format, range, or sourcing detail for that parameter, so the schema carries the full load and the 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?

The description opens with a specific verb and resource ("Lists the API clients of a domain") and then defines the resource precisely as machine callers that exchange a client id + secret for a short-lived token via OAuth 2 client_credentials. That definition implicitly separates it from the API-key siblings (list_domain_api_keys) without naming them, so an agent can tell the two resources apart conceptually.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use or when-not guidance and no named alternative. The only routing hint is embedded in the schema ("from list_domains"), which tells the agent how to obtain the id, not when to prefer this tool over list_domain_api_keys or list_runner_clients.

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