Skip to main content
Glama

List custom domains

render_list_custom_domains
Read-onlyIdempotent

List custom domains for a specific Render service using filters like name, type, verification status, and creation time. Returns matching domains with pagination support.

Instructions

List custom domains. List a particular service's custom domains that match the provided filters. If no filters are provided, all custom domains for the service are returned. Calls GET /services/{serviceId}/custom-domains on the Render Public API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoFilter for the names of custom domain
limitNoThe maximum number of items to return. For details, see [Pagination](https://api-docs.render.com/reference/pagination).
cursorNoThe position in the result list to start from when fetching paginated results. For details, see [Pagination](https://api-docs.render.com/reference/pagination).
serviceIdYesThe ID of the service
domainTypeNoFilter for domain type
createdAfterNoFilter for custom domains created after a certain time (specified as an ISO 8601 timestamp)
createdBeforeNoFilter for custom domains created before a certain time (specified as an ISO 8601 timestamp)
verificationStatusNoFilter for domain verification status (`verified` or `unverified`)
Behavior3/5

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

Annotations already declare readOnly, idempotent, etc. The description adds the API endpoint and filtering behavior, but no additional behavioral traits beyond what annotations provide.

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 concise sentences, front-loaded with purpose, no unnecessary words.

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 main filtering behavior well, mentions API endpoint. Does not explain pagination beyond schema parameter descriptions, but for a read-only list tool, it is mostly complete.

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?

Input schema has 100% description coverage; description does not add meaning beyond filtering logic already implied by schema descriptions. Baseline score of 3 is appropriate.

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 clearly states it lists custom domains and differentiates from sibling tools (create, delete, retrieve, refresh). It specifies the service association and optional filtering.

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?

Provides clear context: requires serviceId and optional filters; explains behavior when no filters are provided. Does not explicitly mention alternatives but siblings make it obvious.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/LuSrodri/render-useful-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server