Skip to main content
Glama

Revoke a domain API client's tokens

revoke_domain_client_tokens
Destructive

Revoke all tokens already issued to a specific domain client from the next request, while keeping the client secret valid. Requires confirm=true; omit or false returns a preview.

Instructions

Refuses every token issued so far to a client, from the next request. The secret keeps working. 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": "revoke_domain_client_tokens"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.53.0

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only declare destructiveHint=true; the description goes well beyond that by disclosing the timing ('from the next request'), the blast radius ('every token issued so far' rather than the client itself), and the important non-effect that the secret remains valid. That is exactly the behavioral context an agent needs before a destructive call.

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 short sentences, each carrying distinct information: effect, scope limitation, and the gating requirement. The most decision-relevant facts are front-loaded with zero 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?

For a destructive, confirm-gated tool with no output schema, the definition covers effect, immediacy, scope, and the secret's survival. It leaves minor gaps — whether the client can simply mint new tokens afterwards, and what the preview returns — but nothing that would cause a misinformed call.

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 schema already documents confirm's preview behaviour and the source of domainId and clientId. The description's 'Requires confirm=true' reinforces the schema but adds no new parameter meaning, so the baseline of 3 applies.

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 names a specific verb and resource — refusing every previously issued token for a client — and adds the crucial scope qualifier 'issued so far', which pins down exactly what is and is not revoked. It also implicitly separates itself from rotate_domain_client_secret by stating the secret itself keeps working.

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 gives a clear operating condition ('Requires confirm=true') and signals the intended scenario via the contrast that the secret survives, which helps an agent choose between this and rotation. There is no explicit statement of when not to use it or a named alternative, so it stops short of full routing guidance.

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