AEO Copilot MCP Server

create_topic

Create a topic cluster to group related prompts, keywords, and target pages, helping organize brand content and drive traffic to chosen URLs.

Instructions

Create a topic cluster for a brand. Topics group related prompts (e.g. 'Pricing Questions', 'Product Comparisons').

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "brandId": "<brandId>",
      "name": "<name>"
    },
    "name": "create_topic"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	Topic name
`pages`	No	Target page URLs that the topic should drive traffic to
`brandId`	Yes	The brand UUID from list_brands
`keywords`	No	Keywords associated with this topic
`description`	No	What this topic covers

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.0Aug 30, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations are provided, so the description carries all behavioral responsibility. It discloses only that it creates a topic cluster, but not what happens on duplicate creation, whether existing brands are required, or what the response contains. A mutation tool with no annotations should give more operational detail.

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?

Two short sentences are front-loaded with the action and resource, and the second sentence earns its place by clarifying the topic concept with concrete examples. No filler.

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?

For a straightforward create operation with fully documented parameters, the description is adequate, but it omits usage guidance and expected result behavior. Since there is no output schema and no annotations, more operational context would make it complete.

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 description coverage is 100%, so the schema already documents all parameters. The description adds the domain concept of topics grouping related prompts, which is helpful but does not add meaning to individual parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a clear verb+resource: create a topic cluster for a brand, and adds the concept that topics group related prompts with examples. It does not explicitly distinguish from siblings like create_index or add_index_topic, but the resource and use case are evident.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus the many sibling tools (e.g. create_index, add_prompts, add_index_topic). No prerequisites or exclusions are mentioned; only the definition is provided.

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