Skip to main content
Glama
brilliantdirectories

brilliant-directories-mcp

Official
by brilliantdirectories
OverviewSchemaRelated ServersScoreDiscussions(1)
JavaScript
Remote

deleteWebPage

DestructiveIdempotent

Permanently delete a web page by its seo_id. Requires confirmation and post-delete cleanup of associated metadata.

Instructions

Delete a page - Permanently delete a web page by seo_id. Destructive - cannot be undone via API.

Use when: permanently removing a page.

Required: seo_id.

Destructive: confirm with the user. If inbound links or menus reference the deleted page's URL, consider creating a createRedirect BEFORE deleting so those links don't 404. Menus with items pointing at this page also need cleanup.

seo_type=data_category cascade — automatic. When the deleted page is data_category, the wrapper auto-deletes its placeholder-slug 301 redirect (response includes _data_category_redirect_deleted: <redirect_id>). The agent does not need to call deleteRedirect manually.

ORPHAN CLEANUP REQUIRED - BD does NOT cascade-delete users_meta rows. Each WebPage with a hero or custom layout has up to 18 EAV rows in users_meta (database=list_seo, database_id=<seo_id>). These persist after deleteWebPage unless you clean them up. Safe post-delete workflow:

  1. Call listUserMeta filtered on database=list_seo AND database_id=<deleted seo_id>.

  2. Client-side filter the response - keep only rows whose database field equals list_seo. The same database_id value may exist in users_meta pointing at unrelated parent tables (e.g. a member with user_id=<seo_id> in users_data), and those rows must NOT be deleted.

  3. For each remaining row, call deleteUserMeta with meta_id=<row.meta_id>, database=list_seo, database_id=<seo_id> (all three required).

Never loop-delete by database_id alone - you will silently destroy unrelated records on other tables.

See also: updateWebPage (modify without removing).

Returns: { status: "success", message: "list_seo record was deleted" }.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
seo_idYesPage primary key

Tool Definition Quality

A4.8/5.0
Behavior5/5

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

Beyond annotations (destructiveHint: true), the description details destructive implications, automatic cascade for data_category, orphan cleanup requirements, and post-deletion workflow. 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 sections, bullet points, and code formatting. Front-loaded with core purpose. Although verbose, each sentence serves a purpose given the tool's destructive nature.

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?

Includes return value, side effects, pre/post conditions, references to related tools, and warnings for a complete understanding. No output schema, but description compensates fully.

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?

Schema covers 100% with a basic description for seo_id. Description adds 'Required: seo_id' and contextual usage throughout, enhancing semantics beyond schema.

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 'Delete a page - Permanently delete a web page by seo_id', specifying the action, resource, and key differentiators like destructive nature and irreversibility. It also distinguishes from siblings by referencing updateWebPage and createRedirect.

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 'Use when: permanently removing a page.' Provides prerequisites (confirm with user, consider redirect), warns against common mistakes (looping by database_id), and lists alternatives (updateWebPage). Comprehensive guidance.

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