Skip to main content
Glama

Update a domain API client

update_domain_client
Destructive

Update a domain client's name, scopes, token lifetime, rate limit, or active state; requires confirm=true, and active:false blocks tokens reversibly without changing the secret.

Instructions

Changes a client's name, scopes, token lifetime, rate limit or active state. active:false refuses its tokens from the next request and is reversible. Never changes the secret (rotate_domain_client_secret). Requires confirm=true.

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>",
      "clientId": "<clientId>"
    },
    "name": "update_domain_client"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
activeNo
scopesNoSpace-separated; replaces the list.
confirmNoMust be true to act. Omit/false returns a preview only.
clientIdYesThe client's id ("dcl_…") — from list_domain_clients.
domainIdYesThe domain's id — from list_domains.
rateLimitPerMinuteNoIts own gateway allowance in requests per minute (1-6000). Every client of a site calls as the site's owner and shares one platform limit, so this keeps one of them from spending the others' share; past it the client gets 429 CLIENT_RATE_LIMIT for the rest of the minute. Omit to keep it; 0 removes it.
tokenLifetimeMinutesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.53.0

TDQS

A4.6/5.0
Behavior5/5

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

Adds substantial behavior beyond the destructiveHint annotation: active:false takes effect from the next request and is reversible, the secret is never touched, and confirm gates a preview. This tells the agent consequence, immediacy, and reversibility for a destructive operation.

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?

Three tight sentences, front-loaded with the scope of change, followed by the reversibility caveat and the confirm requirement. No redundant restatement of the title or name.

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?

Covers the high-risk aspects an agent needs (preview gate, reversibility, secret exclusion) for an 8-parameter destructive tool. The only shortfall is that tokenLifetimeMinutes receives no semantic explanation anywhere.

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?

Adds real meaning for the 'active' flag (refuses tokens, reversible) that the schema does not state. However, tokenLifetimeMinutes is listed as mutable but its unit/semantics are never clarified in either the description or schema, leaving one gap at 63% coverage.

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?

States a specific verb (changes) plus the exact set of mutable fields (name, scopes, token lifetime, rate limit, active state). It also explicitly carves out the secret as out of scope, which separates it from rotate_domain_client_secret.

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?

Explicitly routes secret changes to rotate_domain_client_secret and states that confirm=true is required to act, with false/omitted producing a preview. Lacks a fuller statement of when this tool is preferable to siblings like update_domain_api_key, but the core routing is clear.

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