Skip to main content
Glama

List domains

list-domains
Read-only

List the domains tracked in the workspace, primary first. Returns an array with id, domain, name, status and sitemap_scan_status; the id is the domain_id other tools take. get-domain returns one domain with more fields.

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

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover read-only/non-destructive/closed-world, so the description adds value by disclosing the return shape (id, domain, name, status, sitemap_scan_status) and the 'primary first' ordering — neither of which is in any structured field since there is no output schema. It does not mention pagination or result-size limits, which is the remaining gap.

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?

Two tight sentences: the first gives the scope and ordering, the second gives the return fields, the id mapping, and the sibling pointer. Nothing is wasted and the most important fact (it lists all domains) leads.

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?

With no output schema and no parameters, the description carries the return-value burden and does so adequately, including the crucial note that 'id is the domain_id other tools take'. Missing only edge-case behavior (empty workspace, truncation) to be fully complete.

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?

The tool takes zero parameters, so per the baseline this scores 4. The description correctly implies no input is required by describing only output.

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 ('List the domains tracked in the workspace') plus the ordering rule ('primary first'). It also implicitly distinguishes itself from the similarly-named get-domain by scope (all vs one).

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 the agent to get-domain when more fields per domain are needed, which is a real alternative-selection signal. It stops short of saying when listing is the wrong starting point (e.g., if the agent already knows a domain_id), but the guidance is clear.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources