Skip to main content
Glama

List DNS Records

list_dns_records
Read-onlyIdempotent

Retrieve, search, sort, and filter DNS records in a Cloudflare zone to inspect configurations without making changes. Use filters for name, type, content, and tags.

Instructions

List, search, sort, and filter a zones' DNS records. Read operation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagNoCondition on the DNS record tag. Parameter values can be of the form `<tag-name>:<tag-value>` to search for an exact `name:value` pair, or just `<tag-name>` to search for records with a specific tag name regardless of its value. This is a convenience shorthand for the more powerful `tag.<predicate>` parameters. Examples: - `tag=important` is equivalent to `tag.present=important` - `tag=team:DNS` is equivalent to `tag.exact=team:DNS`
nameNoExact value of the DNS record name. This is a convenience alias for `name.exact`.
pageNo
typeNo
matchNo
orderNo
searchNo
accountNoExact private profile label. Account/zone defaults route inputs; token permissions remain provider controlled.
commentNoExact value of the DNS record comment. This is a convenience alias for `comment.exact`.
contentNoExact value of the DNS record content. This is a convenience alias for `content.exact`.
proxiedNo
zone_idNo
per_pageNo
directionNo
tag_exactNoA tag and value, of the form `<tag-name>:<tag-value>`. The API will only return DNS records that have a tag named `<tag-name>` whose value is `<tag-value>`. Tag filters are case-insensitive.
tag_matchNo
name_exactNoExact value of the DNS record name. Name filters are case-insensitive.
tag_absentNoName of a tag which must *not* be present on the DNS record. Tag filters are case-insensitive.
tag_presentNoName of a tag which must be present on the DNS record. Tag filters are case-insensitive.
tag_containsNoA tag and value, of the form `<tag-name>:<tag-value>`. The API will only return DNS records that have a tag named `<tag-name>` whose value contains `<tag-value>`. Tag filters are case-insensitive.
tag_endswithNoA tag and value, of the form `<tag-name>:<tag-value>`. The API will only return DNS records that have a tag named `<tag-name>` whose value ends with `<tag-value>`. Tag filters are case-insensitive.
comment_exactNoExact value of the DNS record comment. Comment filters are case-insensitive.
content_exactNoExact value of the DNS record content. Content filters are case-insensitive.
name_containsNoSubstring of the DNS record name. Name filters are case-insensitive.
name_endswithNoSuffix of the DNS record name. Name filters are case-insensitive.
comment_absentNoIf this parameter is present, only records *without* a comment are returned.
shadowing_nameNoReturns NS records that shadow the given name, searching at the name itself and each of its ancestor names within the zone, excluding the zone apex. The value must be a subdomain of the zone; the zone apex is not accepted. See [Shadowed records](https://developers.cloudflare.com/dns/manage-dns-records/reference/shadowed-records).
tag_startswithNoA tag and value, of the form `<tag-name>:<tag-value>`. The API will only return DNS records that have a tag named `<tag-name>` whose value starts with `<tag-value>`. Tag filters are case-insensitive.
comment_presentNoIf this parameter is present, only records *with* a comment are returned.
name_startswithNoPrefix of the DNS record name. Name filters are case-insensitive.
comment_containsNoSubstring of the DNS record comment. Comment filters are case-insensitive.
comment_endswithNoSuffix of the DNS record comment. Comment filters are case-insensitive.
content_containsNoSubstring of the DNS record content. Content filters are case-insensitive.
content_endswithNoSuffix of the DNS record content. Content filters are case-insensitive.
shadowed_by_nameNoFilters the response to records at or below the specified NS delegation name. NS, DS, and NSEC records at the delegation name are excluded because they are not shadowed by that delegation. Those record types are included only when they exist below the delegation. The value must be a non-apex subdomain of the zone. Requires `include_shadow_metadata=true`. See [Shadowed records](https://developers.cloudflare.com/dns/manage-dns-records/reference/shadowed-records).
comment_startswithNoPrefix of the DNS record comment. Comment filters are case-insensitive.
content_startswithNoPrefix of the DNS record content. Content filters are case-insensitive.
include_shadow_metadataNoWhether to include shadow metadata in the `meta` field of each record in the response. See [Shadowed records](https://developers.cloudflare.com/dns/manage-dns-records/reference/shadowed-records).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

C2.9/5.0
Behavior2/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description's 'Read operation' simply repeats the readOnly annotation and adds no new behavioral context such as pagination behavior, filter interaction, or authentication requirements. With annotations covering safety, this adds no value.

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?

The description is two short sentences and front-loads the purpose. The second sentence is redundant with the annotations, so it does not fully earn its place, but the overall brevity is appropriate.

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

Completeness3/5

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

For a complex tool with 38 parameters, the description is minimal but sufficient to understand its core purpose. Rich annotations cover the safety profile and the schema documents most parameters, yet the description does not address filtering alternatives, pagination expectations, or the shadowing parameters, leaving some contextual gaps.

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 description coverage is 74%, and most parameters have detailed descriptions in the schema (including $ref definitions) covering filtering, sorting, and pagination semantics. The description only mentions 'search, sort, and filter' in generic terms and adds no syntax or interaction details beyond what the schema already provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's action (list/search/sort/filter) and resource (DNS records), distinguishing it from single-record siblings like get_dns_record. However, it does not explicitly name an alternative or scope boundary, so it lacks the sibling differentiation that would earn a 5.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus alternatives such as get_dns_record, nor any prerequisites or exclusions. The only contextual note, 'Read operation,' describes the operation type but does not help an agent choose among siblings.

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