Skip to main content
Glama

seo_generate_side_page

Generate SEO side pages for landing pages to strengthen topical authority and target cluster keywords. Use freeform prompts or structured briefs; async generation returns an operation ID to poll.

Instructions

Generates a side page for a brand's landing page, optionally linked to an SEO cluster (clusterId). When linked, the side page surfaces in cluster-context queries and inherits the cluster's keyword targeting — strengthening topical authority that feeds GEO citation patterns. Two body modes: • freeform: pass key + prompt (+ optional keywords, selectedSections, voiceProfileId, sidePageType). Freeform now writes real section-level content (hero/features/showcase/faq/cta), not just metadata. • brief: pass key + brief (structured outline) + optional briefId and roadmapItemId. Typically takes ~2–5 min. Async — returns { success, operationId, operationRowId, pollUrl, sidePageId }. Poll get_job with the returned operationId until state is completed (or failed/partially_failed/cancelled on error); the generated page's sections will be populated once complete. Comparison-type briefs run synchronously and return sidePageId directly. slug is the PARENT landing page slug under which the side page is created.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYesSide-page key (URL slug fragment under the parent LP)
slugYesParent landing page slug
briefNoBrief-mode structured outline. When set, this is the canonical payload.
promptNoFreeform-mode generation prompt (omit when passing `brief`)
briefIdNoPersisted SeoBrief ID — required for comparison-type generation
keywordsNoFreeform-mode: target keywords to weave into the page
clusterIdNoSEO KeywordCluster ID to link this side page to (maps to SidePage.sourceClusterId)
sidePageTypeNoDefaults to 'landing'. Use 'comparison' only with a persisted comparison briefId.
roadmapItemIdNoRoadmap item ID this side page is fulfilling
voiceProfileIdNoVoice profile to write in
autoAssignAssetsNoAuto-assign brand assets to image slots after generation
selectedSectionsNoFreeform-mode: restrict generation to these section ids (e.g. hero, features, showcase, faq, cta, pricing). Omit to generate all default sections.
Behavior4/5

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

No annotations are provided, so the description carries the burden. It discloses async processing, expected duration (~2–5 min), the return payload, and the synchronous exception for comparison-type briefs. Also clarifies that freeform generates actual section-level content and specifies slug semantics. This is strong coverage of behavioral traits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with a clear opening, bulleted modes, and a closing clarification. Every sentence adds useful information without fluff. Appropriate length for the tool's complexity, and key information is front-loaded.

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?

For a complex async creation tool with no output schema, the description covers return values, polling instructions, error states, modes, and the SEO linkage benefit. It also specifies the parent slug requirement. Minimal gaps remain, and any missing lifecycle details are likely covered by sibling tools.

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?

Despite 100% schema coverage, the description adds significant value by organizing parameters into usage modes (freeform vs brief), explaining which optional params belong to each mode, and clarifying that comparison-type briefs require a persisted briefId. It also reinforces key parameter relationships (key+prompt vs key+brief) beyond the 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?

Clearly states it generates a side page for a landing page, with optional SEO cluster linkage. Distinct from generic side page generation by emphasizing cluster-context queries, keyword inheritance, and GEO authority. Verb+resource+scope is explicit.

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?

Provides mode-specific parameter usage (freeform vs brief) and async behavior, including when to poll get_job and when comparison briefs run synchronously. Does not explicitly contrast with generic generate_side_page or other alternatives, but the SEO context implies its niche.

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/bitsandtea/postking-mcp'

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