prompteye-mcp

Official

Overview Schema Source Related Servers Discussions Admin

Build a topical authority map for a topic

create_topical_map

Build a pillar-and-clusters content plan for a topic: one compendium page plus supporting article titles grouped by category, to cover a subject for search engines and AI models.

Instructions

Builds a pillar-and-clusters content plan for a topic in the active project: one compendium page and the supporting article titles underneath it, grouped by category, meant to make the site the topic's most complete source for both search engines and AI models.

Building one takes a little while, since it asks a model to plan the whole structure. The map comes back processing and turns ready once that finishes, or error if it fails — read it with get_topical_map until it does.

Every call starts a new map; there is no limit on how many a project can have.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`topic`	Yes	The topic to build a map for, e.g. 'cloud backup for small teams'.
`language`	Yes	Language to write the map in, as a two-letter code such as en or pl.

Output Schema

TableJSON Schema

Name	Required	Description
`id`	Yes
`topic`	Yes
`pillar`	Yes	The compendium page. null until ready.
`status`	Yes	processing the moment it is requested, then ready — pillar and clusters filled in — or error, see errorMessage.
`clusters`	Yes	The supporting article titles, grouped by category. Empty until ready.
`language`	Yes
`createdAt`	Yes	When the map was requested, ISO 8601 in UTC.
`projectId`	Yes
`errorMessage`	Yes	Why generation failed. null unless status is error.
`generationCost`	Yes	Cost of the generation, in USD.

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.0.22Oct 2, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Adds substantial behavior beyond the annotations: the call is slow because it invokes a model, it returns asynchronously with `processing`/`ready`/`error` states, and it must be polled with get_topical_map. It also confirms the non-idempotent semantics ('every call starts a new map; no limit'), reinforcing idempotentHint=false.

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?

Front-loads what the tool produces, then the async lifecycle, then the repeat-call behavior — good ordering. The 'most complete source for both search engines and AI models' clause is mildly promotional rather than operational, but overall the text is tight.

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?

An output schema exists, so return values need no explanation, and the description still supplies the one thing an agent must know to call this correctly: it is async and must be polled. Nothing material is missing.

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 both parameters fully described (topic example, two-letter language code), so the schema carries parameter meaning. The description adds no further syntax or format detail, making the baseline 3 appropriate.

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?

States a concrete verb and artifact ('Builds a pillar-and-clusters content plan... one compendium page and supporting article titles, grouped by category'). It is clearly distinguishable from siblings get_topical_map, list_topical_maps, and regenerate_topical_map_cluster.

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?

Explains the operating context ('for a topic in the active project') and the follow-up read path via get_topical_map. It does not explicitly state when NOT to use it (e.g. when a map already exists), but the 'every call starts a new map' note covers the main alternative decision.

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

Deploy Server