Skip to main content
Glama

List a domain's API keys

list_domain_api_keys
Read-only

Lists all API keys for a domain with masked values and metadata so you can audit key status and expiration; create or rotate a key when you need usable plaintext credentials.

Instructions

Lists the API keys on a domain (id, name, MASKED key, createdAt, expiresAt, isActive, lastUsedAt) — the plaintext key is never shown here, only at create/rotate time. Use create_domain_api_key to get one a caller can actually use against a non-anonymous endpoint.

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_api_keys"
  }
}

Input Schema

NameRequiredDescriptionDefault
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 readOnlyHint=true; the description goes further by disclosing a security-relevant behavior the agent could not otherwise know — keys come back MASKED and the plaintext is only available at create/rotate time. It also enumerates the returned fields (id, name, createdAt, expiresAt, isActive, lastUsedAt), which compensates for the absence of an output schema.

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?

Two tight sentences with no filler, and the core purpose plus the field list are front-loaded before the caveat. Slight density in the parenthetical field list, but every element carries information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter read-only list tool, the description covers purpose, returned fields, a masking caveat, and the correct sibling for the adjacent need. Nothing an agent needs in order to call this correctly is missing.

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 domainId parameter already carries a description pointing to list_domains. The description adds no further parameter meaning, which is the appropriate baseline when the schema does the work.

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 and resource ("Lists the API keys on a domain") and immediately enumerates the returned fields, which pins down the scope precisely. It is clearly distinguishable from the sibling create/rotate/delete/update key tools.

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 names a concrete alternative and the condition that selects it: use create_domain_api_key when a caller needs a key that actually works against a non-anonymous endpoint. That implicitly tells the agent what this tool is NOT for (obtaining usable credentials), though it does not spell out a positive use case such as auditing or inspecting existing keys.

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