Skip to main content
Glama
brilliantdirectories

brilliant-directories-mcp

Official
by brilliantdirectories
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

getWebPage

Read-onlyIdempotent

Fetch a single web page's metadata and content by its SEO ID. Use to read the current page before making edits.

Instructions

Get a single page - Fetch a single web page by seo_id. Read-only.

Use when: fetching one page's metadata (+ optionally its body/CSS/JS) before editing. Common for "let me read the current About page before editing it" workflows.

Required: seo_id (path).

Lean-by-default keep-list: same shape as listWebPages — returns 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. 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.).

Before updateWebPage edits to body, CSS, head, or footer HTML/JS, pass the matching flag so you have the current value to modify. Hero edits require include_extras=1 to read the existing hero_* values first.

See also: listWebPages (enumerate), updateWebPage (modify).

Returns: { status: "success", message: [{...record}] } - the message array contains 1 lean-shaped record when found.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
seo_idYesPage primary key
include_contentNoOpt in to return the `content` (body HTML) field. Default stripped.
include_codeNoOpt in to return `content_css`, `content_head`, `content_footer_html`. 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.

Tool Definition Quality

A4.7/5.0
Behavior5/5

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

Adds rich behavioral context beyond annotations: lean-by-default return shape, flags to include content/code/extras, and prerequisite for updateWebPage edits. No contradictions with annotations.

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?

Well-structured with clear headings and bullet points, but slightly verbose. Every sentence adds value, and the description is front-loaded with purpose.

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?

Comprehensive for a get tool: covers return format, lean default, flags, and prerequisites for updates. Annotations and schema cover safety and parameters, so description fills remaining gaps.

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?

Adds significant meaning beyond the schema's parameter descriptions. Explains the lean default, what each include_flag restores, and practical usage like hero edits needing include_extras=1. Schema coverage is 100%, but description enhances it.

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 the tool fetches a single web page by seo_id and is read-only. It distinguishes itself from siblings like listWebPages and updateWebPage by specifying the use case and resource scope.

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 provides a use case ('fetching one page's metadata before editing') and required parameter (seo_id). Mentions read-only but does not explicitly state when not to use or provide alternatives beyond listing sibling tools.

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