Skip to main content
Glama
sharozdawa

content-optimizer-mcp

find_missing_topics

Identifies content gaps by comparing your text with SERP competitors, showing missing topics and coverage percentage to improve SEO.

Instructions

Find topics from SERP competitors that are missing in your content. Returns covered topics, missing topics, and coverage percentage.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contentYesThe content to check
keywordYesThe target keyword

Implementation Reference

  • The handler implementation for the 'find_missing_topics' tool, which compares provided content against keywords and identifies missing topics.
    async ({ content, keyword }) => {
      const topics = getKeywordTopics(keyword);
      const contentLower = content.toLowerCase();
    
      const covered: string[] = [];
      const missing: string[] = [];
    
      for (const topic of topics) {
        if (contentLower.includes(topic.toLowerCase())) {
          covered.push(topic);
        } else {
          missing.push(topic);
        }
      }
    
      const coverage = topics.length > 0 ? (covered.length / topics.length) * 100 : 0;
    
      let assessment: string;
      if (coverage >= 80) assessment = "Excellent topic coverage — your content is comprehensive.";
      else if (coverage >= 60) assessment = "Good coverage — a few more topics would strengthen the content.";
      else if (coverage >= 40) assessment = "Moderate coverage — significant topics are missing.";
      else assessment = "Low coverage — many important topics are not addressed.";
    
      return {
        content: [
          {
            type: "text" as const,
            text: JSON.stringify({
              keyword,
              totalTopics: topics.length,
              coveredTopics: covered,
              missingTopics: missing,
              coveragePercentage: Math.round(coverage),
              assessment,
              recommendations: missing.slice(0, 7).map((t) => `Add a section or paragraph covering "${t}".`),
            }, null, 2),
          },
        ],
      };
    }
  • Registration of the 'find_missing_topics' tool, including its description and input schema.
    server.tool(
      "find_missing_topics",
      "Find topics from SERP competitors that are missing in your content. Returns covered topics, missing topics, and coverage percentage.",
      {
        content: z.string().describe("The content to check"),
        keyword: z.string().describe("The target keyword"),
      },
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions the tool returns 'covered topics, missing topics, and coverage percentage,' which gives some insight into output structure. However, it lacks details on how it identifies SERP competitors, what constitutes a 'topic,' potential rate limits, or error conditions, making behavioral understanding incomplete.

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 and front-loaded, stating the core purpose in the first sentence and the return values in the second. Both sentences earn their place by providing essential information without redundancy. However, it could be slightly more structured by explicitly separating purpose from output details.

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 (analyzing SERP competitors and content gaps), lack of annotations, and no output schema, the description is minimally adequate. It covers the basic purpose and output types but lacks depth on how the analysis works, data sources, or limitations. For a tool with no structured behavioral hints, this leaves gaps in contextual understanding.

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 both parameters ('content' and 'keyword'). The description adds no additional semantic meaning beyond what the schema provides, such as examples or constraints. With high schema coverage, the baseline score of 3 is appropriate as the description doesn't compensate but also doesn't detract.

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?

The description clearly states the tool's purpose: 'Find topics from SERP competitors that are missing in your content.' It specifies the action (find), source (SERP competitors), and target (your content). However, it doesn't explicitly differentiate from sibling tools like 'analyze_keyword' or 'get_content_recommendations,' which might have overlapping functionality.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, ideal scenarios, or exclusions. For example, it doesn't clarify if this should be used before or after tools like 'analyze_keyword' or 'score_content,' leaving usage context implied but unspecified.

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/sharozdawa/content-optimizer'

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