Skip to main content
Glama

List your API domains

list_domains
Read-only

Retrieve API domains available for deploying endpoints, including IDs for deploy_endpoint, with optional workspace filtering and name/slug search.

Instructions

Lists the API domains you can deploy endpoints into (id, name, slug, baseUrl). Use the returned id as deploy_endpoint's domainId. Pass workspaceId to list the domains usable for a specific workspace (e.g. a shared one — the owner's domains). If empty, create one with create_domain — no UI step needed.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
queryNoFilter domains by name/slug.
workspaceIdNoList domains deployable for this workspace (its owner's).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.53.0

TDQS

A4.7/5.0
Behavior4/5

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

readOnlyHint=true already establishes the safety profile, and the description adds real value on top: it discloses the returned fields, the semantics of listing per-workspace (owner's domains, shared ones), and the empty-result remediation. It stops short of pagination or scope limits, but for a read-only list tool that is a minor omission.

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 compact sentences, each doing distinct work: purpose plus return shape first, then the chaining hint, then the workspace filter, then the empty-state remedy. No filler or repetition of the title.

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?

With no output schema, the description compensates by naming the returned fields, and with only two optional parameters it covers workspaceId semantics and the empty-result path. An agent has everything needed to call this correctly and act on the result.

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?

Schema coverage is 100%, so the baseline is 3; the description earns an extra point by clarifying what workspaceId really selects — the domains deployable for that workspace, including shared domains owned by someone else — which the schema's terse "its owner's" wording only hints at. The query parameter is left to the schema.

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 domains you can deploy endpoints into") and enumerates the returned fields (id, name, slug, baseUrl), so the agent knows exactly what it gets back and how it differs from unrelated list tools such as list_workspaces.

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

Usage Guidelines5/5

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

Explicitly routes downstream usage ("Use the returned id as deploy_endpoint's domainId"), explains when to pass workspaceId, and covers the empty-result case by directing the agent to create_domain with a note that no UI step is needed. When-to-use, what-to-do-next, and the failure fallback are all present.

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