Skip to main content
Glama
Sign In
bricks-mcp

bricks-mcp

by developer2013
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

bricks_seo_auto_fix

Generate missing SEO metadata for pages in Bricks. Creates title, meta description, canonical URL, and og:type from page content for pages lacking them.

Instructions

Auto-generate missing SEO data from page content. Creates SEO title (from post title), meta description (from first text content), canonical URL, and og:type for pages that lack them.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "bricks_seo_auto_fix"
  }
}

Input Schema

NameRequiredDescriptionDefault
allNoSet true to fix ALL published pages
dry_runNoPreview changes without saving (default: false)
page_idsNoArray of page IDs to fix

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.3

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description must convey behavioral traits. It does not explain side effects like whether it overwrites existing data (though 'for pages that lack them' suggests it only adds missing) or what happens with conflicting parameters. The description lacks explicit behavior for parameters like all and dry_run.

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 concise, consisting of two sentences that convey the core functionality. It is front-loaded and avoids unnecessary detail. Could be improved by including a brief note on parameters or use cases, but it is not overly verbose.

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?

Given the tool's complexity (3 parameters, no output schema), the description covers the main action but lacks details on return values, parameter interactions (e.g., both all and page_ids set), and error handling. It is adequate but not fully comprehensive.

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 coverage is 100% with clear parameter descriptions for all, dry_run, and page_ids. The tool description adds no additional meaning beyond the schema. Thus, it meets the baseline for parameter semantics.

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's purpose: auto-generating missing SEO data from page content. It specifies the verb (auto-generate), the resource (missing SEO data), and lists the generated fields (SEO title, meta description, canonical URL, og:type). This distinguishes it from sibling tools like bricks_seo_analyze or bricks_update_page_seo.

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?

The description implies when to use the tool: for pages that lack SEO data ('for pages that lack them'). It does not explicitly mention alternatives like bricks_update_page_seo or bricks_seo_bulk_update, but the condition 'auto-generate' and 'missing' provides clear context for usage.

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

Deploy Server

Other Tools