Skip to main content
Glama
SEO-Review-Tools

SEO Review Tools - MCP server

Official

get_seo_content_score

Analyze content SEO performance by evaluating title tags, meta descriptions, body content, and keywords to identify optimization opportunities.

Instructions

Get the SEO content score from SEO Review Tools.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
title_tagYesThe title tag of the content.
meta_descriptionYesThe meta description of the content.
body_contentYesThe body content of the document, including HTML formatting.
keywordYesThe main keyword for the SEO analysis.
relatedkeywordsYesRelated keywords for the SEO analysis.

Implementation Reference

  • The core handler function `executeFunction` that makes the API request to SEO Review Tools to compute the SEO content score based on provided title, meta, body, keyword, and related keywords.
    const executeFunction = async ({ title_tag, meta_description, body_content, keyword, relatedkeywords }) => {
      const baseUrl = 'https://api.seoreviewtools.com/v5/seo-content-optimization/';
      const token = process.env.SEO_API_WORKSPACE_API_KEY;
      const content_input = {
        title_tag,
        meta_description,
        body_content
      };
    
      try {
        // Construct the URL with query parameters
        const url = new URL(baseUrl);
        url.searchParams.append('content', '1');
        url.searchParams.append('keyword', keyword);
        url.searchParams.append('relatedkeywords', relatedkeywords.join('|'));
        url.searchParams.append('key', token);
    
        // Set up headers for the request
        const headers = {
          'Content-Type': 'application/json'
        };
    
        // Perform the fetch request
        const response = await fetch(url.toString(), {
          method: 'POST',
          headers,
          body: JSON.stringify({ content_input })
        });
    
        // Check if the response was successful
        if (!response.ok) {
          const errorData = await response.json();
          throw new Error(errorData);
        }
    
        // Parse and return the response data
        const data = await response.json();
        return data;
      } catch (error) {
        console.error('Error getting SEO content score:', error);
        return { error: 'An error occurred while getting the SEO content score.' };
      }
    };
  • The JSON schema definition for the tool, including name, description, parameters, and required fields.
      type: 'function',
      function: {
        name: 'get_seo_content_score',
        description: 'Get the SEO content score from SEO Review Tools.',
        parameters: {
          type: 'object',
          properties: {
            title_tag: {
              type: 'string',
              description: 'The title tag of the content.'
            },
            meta_description: {
              type: 'string',
              description: 'The meta description of the content.'
            },
            body_content: {
              type: 'string',
              description: 'The body content of the document, including HTML formatting.'
            },
            keyword: {
              type: 'string',
              description: 'The main keyword for the SEO analysis.'
            },
            relatedkeywords: {
              type: 'array',
              items: {
                type: 'string'
              },
              description: 'Related keywords for the SEO analysis.'
            }
          },
          required: ['title_tag', 'meta_description', 'body_content', 'keyword', 'relatedkeywords']
        }
      }
    }
  • lib/tools.js:7-16 (registration)
    The `discoverTools` function dynamically imports all tools listed in toolPaths, including this one, by loading module.apiTool and registering it for use.
    export async function discoverTools() {
      const toolPromises = toolPaths.map(async (file) => {
        const module = await import(`../tools/${file}`);
        return {
          ...module.apiTool,
          path: file,
        };
      });
      return Promise.all(toolPromises);
    }
  • tools/paths.js:7-7 (registration)
    The path to this specific tool file, used by discoverTools for dynamic import and registration.
    'seo-api-workspace/seo-ap-is-seo-review-tools/get-seo-content-score.js',
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 only states the action ('Get') without details on rate limits, authentication needs, response format, or potential side effects. This is inadequate for a tool with 5 required parameters and no output schema.

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 a single, efficient sentence with zero waste. It is appropriately sized and front-loaded, clearly stating the tool's purpose without unnecessary elaboration.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity (5 required parameters) and lack of annotations or output schema, the description is incomplete. It does not explain what the SEO content score entails, how it is calculated, or what the return values look like, leaving significant gaps for agent 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 fully documents all 5 parameters. The description adds no additional meaning about parameters, such as format examples or usage context, but the schema provides sufficient baseline information.

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

Purpose3/5

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

The description states the tool 'Get[s] the SEO content score from SEO Review Tools', which provides a clear verb ('Get') and resource ('SEO content score'). However, it lacks specificity about what the score measures or how it differs from sibling tools like get_authority_scores or get_keyword_statistics, making it somewhat vague.

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 is provided on when to use this tool versus alternatives. The description does not mention context, prerequisites, or exclusions, leaving the agent to infer usage based on the tool name alone.

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/SEO-Review-Tools/SEO-API-MCP'

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