Skip to main content
Glama
brilliantdirectories

brilliant-directories-mcp

Official

listWebPages

Read-onlyIdempotent

List all static and SEO pages on your directory site with paginated enumeration. Filter by type, sort columns, and opt into additional fields like content or code.

Instructions

List pages (list_seo) - Paginated enumeration of web pages (list_seo records). Read-only.

Returns every static/SEO page on the site - homepage, about, contact, custom landing pages, templates, etc. Filter by seo_type to get pages of a specific type (e.g., only content pages).

Use when: listing all site pages. Filter by seo_type to scope. For one page by seo_id use getWebPage.

Pagination: cursor-based (limit, page). See Rule: Pagination.

Filter/sort: property+property_value+property_operator, order_column+order_type. See Rule: Filter operators.

Lean-by-default keep-list: rows return only the core identity + linkage fields: seo_id, seo_type, filename, title, h1, h2, nickname, linked_post_category, linked_post_type, date_updated, revision_timestamp. Everything else is stripped — restore via flags:

  • include_content=1 - return content (body HTML).

  • include_code=1 - return content_css, content_head, content_footer_html.

  • include_extras=1 - return everything else (all hero_* fields, meta_desc, meta_keywords, seo_text, facebook_*, content_layout, content_sidebar, menu_layout, all hide_* toggles, master_id, content_active, database, section, custom_html_placement, etc.).

On sites with heavy pages, a single row can be 10-30KB with code assets; opt in only when you actually need the data (e.g. before updateWebPage edits to body/CSS/JS, or when reading hero config to display it).

See also: getWebPage (single by ID), createWebPage, updateWebPage.

Returns: { status: "success", total, ..., message: [...records] }.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
include_contentNoOpt in to return the `content` (body HTML) field on each row. Default stripped.
include_codeNoOpt in to return `content_css`, `content_head`, `content_footer_html` on each row. Default stripped. Needed before `updateWebPage` edits to CSS/head/JS.
include_extrasNoOpt in to return ALL remaining fields on this resource that are not in the lean-by-default keep-list and not gated by another `include_*` flag. Lean default returns only the core identity, routing, and load-bearing fields. `include_extras=1` restores everything else (geo, all hero_*, layout/sidebar/menu config, all display toggles, admin metadata, etc.). Resource-specific — see each tool's description for what the extras bundle contains.
limitNoRecords per page (default 25, max 100)
pageNoPagination cursor (use next_page from previous response)
propertyNoField name to filter by
property_valueNoValue to filter by
property_operatorNoFilter operator (word-form; symbol forms WAF-stripped). Single: eq, ne, lt, lte, gt, gte, like, not_like. CSV: in, not_in, between. Substring: contains, starts_with, ends_with (+not_). Date: year_eq, month_eq, day_eq (+not_), since_days, until_days. Length: length_eq, length_lt, length_gt, length_between. Null: is_set, is_not_set, is_null, is_not_null. See Rule: Filter operators for value shapes.
order_columnNoColumn to sort by
order_typeNoSort direction: ASC or DESC
Behavior4/5

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

Annotations already provide readOnlyHint, destructiveHint, idempotentHint, openWorldHint. The description adds context about lean-by-default behavior, pagination method, and return format structure. No contradiction, but the description reinforces and elaborates on the read-only nature.

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 well-structured with sections, bullet points, and a clear hierarchy. It is somewhat verbose but front-loaded with key information. Every sentence adds value, though some details could be condensed.

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?

Given the tool's complexity (10 parameters, no output schema), the description is highly complete. It covers pagination, filtering, opt-in flags, return format, and cross-references to related tools and rules. No gaps are evident.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with descriptions for all 10 parameters. The description adds significant meaning beyond schema by explaining the purpose of include_* flags, the keep-list behavior, and the context for using them. It also clarifies pagination cursors and filter operators.

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 that the tool lists web pages (list_seo records) and enumerates static/SEO pages. It distinguishes from siblings by referencing getWebPage for single page retrieval and mentions filtering by seo_type.

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 states when to use: 'listing all site pages'. Provides guidance on filtering, pagination, and opt-in flags for content/code/extras. Also notes when to use getWebPage instead, and when to include content before updateWebPage edits.

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/brilliantdirectories/brilliant-directories-mcp'

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