Skip to main content
Glama
ravinwebsurgeon

DataForSEO MCP Server

content_analysis_summary

Analyze citation data for target keywords to understand SEO performance, filter by page types and sentiment thresholds, and extract actionable insights from content analysis.

Instructions

This endpoint will provide you with an overview of citation data available for the target keyword

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keywordYestarget keyword Note: to match an exact phrase instead of a stand-alone keyword, use double quotes and backslashes;
keyword_fieldsNotarget keyword fields and target keywords use this parameter to filter the dataset by keywords that certain fields should contain; you can indicate several fields; Note: to match an exact phrase instead of a stand-alone keyword, use double quotes and backslashes; example: { "snippet": "\"logitech mouse\"", "main_title": "sale" }
page_typeNotarget page types
initial_dataset_filtersNoinitial dataset filtering parameters initial filtering parameters that apply to fields in the Search endpoint; you can add several filters at once (8 filters maximum); you should set a logical operator and, or between the conditions; the following operators are supported: regex, not_regex, <, <=, >, >=, =, <>, in, not_in, like,not_like, has, has_not, match, not_match you can use the % operator with like and not_like to match any string of zero or more characters; example: ["domain","<>", "logitech.com"] [["domain","<>","logitech.com"],"and",["content_info.connotation_types.negative",">",1000]] [["domain","<>","logitech.com"]], "and", [["content_info.connotation_types.negative",">",1000], "or", ["content_info.text_category","has",10994]]
positive_connotation_thresholdNopositive connotation threshold specified as the probability index threshold for positive sentiment related to the citation content if you specify this field, connotation_types object in the response will only contain data on citations with positive sentiment probability more than or equal to the specified value
sentiments_connotation_thresholdNosentiment connotation threshold specified as the probability index threshold for sentiment connotations related to the citation content if you specify this field, sentiment_connotations object in the response will only contain data on citations where the probability per each sentiment is more than or equal to the specified value
internal_list_limitNomaximum number of elements within internal arrays you can use this field to limit the number of elements within the following arrays

Implementation Reference

  • The main execution logic of the tool: formats parameters, sends POST request to DataForSEO /v3/content_analysis/summary/live endpoint, handles response or error.
    async handle(params: any): Promise<any> {
      try {
        const response = await this.dataForSEOClient.makeRequest('/v3/content_analysis/summary/live', 'POST', [{
          keyword: params.keyword,
          keyword_fields: params.keyword_fields,
          page_type: params.page_type,
          initial_dataset_filters: this.formatFilters(params.initial_dataset_filters),
          positive_connotation_threshold: params.positive_connotation_threshold,
          sentiments_connotation_threshold: params.sentiments_connotation_threshold,
          internal_list_limit: params.internal_list_limit
        }]);
        return this.validateAndFormatResponse(response);
      } catch (error) {
        return this.formatErrorResponse(error);
      }
    }
  • Zod schema defining input parameters such as keyword, keyword_fields, page_type, initial_dataset_filters, connotation thresholds, and internal_list_limit.
      getParams(): z.ZodRawShape {
        return {
          keyword: z.string().describe(`target keyword
            Note: to match an exact phrase instead of a stand-alone keyword, use double quotes and backslashes;`),
          keyword_fields: z.object({
            title: z.string().optional(),
            main_title: z.string().optional(),
            previous_title: z.string().optional(),
            snippet: z.string().optional()
          }).optional().describe(
            `target keyword fields and target keywords
            use this parameter to filter the dataset by keywords that certain fields should contain;
            you can indicate several fields;
            Note: to match an exact phrase instead of a stand-alone keyword, use double quotes and backslashes;
            example:
            {
              "snippet": "\\"logitech mouse\\"",
              "main_title": "sale"
            }`
          ),
          page_type: z.array(z.enum(['ecommerce','news','blogs', 'message-boards','organization'])).optional().describe(`target page types`),
          initial_dataset_filters: z.array(
            z.union([
              z.array(z.union([z.string(), z.number(), z.boolean()])).length(3),
              z.enum(["and", "or"])
            ])
          ).max(8).optional().describe(
            `initial dataset filtering parameters
            initial filtering parameters that apply to fields in the Search endpoint;
            you can add several filters at once (8 filters maximum);
            you should set a logical operator and, or between the conditions;
            the following operators are supported:
            regex, not_regex, <, <=, >, >=, =, <>, in, not_in, like,not_like, has, has_not, match, not_match
            you can use the % operator with like and not_like to match any string of zero or more characters;
            example:
            ["domain","<>", "logitech.com"]
            [["domain","<>","logitech.com"],"and",["content_info.connotation_types.negative",">",1000]]
    
            [["domain","<>","logitech.com"]],
            "and",
            [["content_info.connotation_types.negative",">",1000],
            "or",
            ["content_info.text_category","has",10994]]`
          ),
          positive_connotation_threshold: z.number()
            .describe(`positive connotation threshold
              specified as the probability index threshold for positive sentiment related to the citation content
              if you specify this field, connotation_types object in the response will only contain data on citations with positive sentiment probability more than or equal to the specified value`).min(0).max(1).optional().default(0.4),
          sentiments_connotation_threshold: z.number()
            .describe(`sentiment connotation threshold
    specified as the probability index threshold for sentiment connotations related to the citation content
    if you specify this field, sentiment_connotations object in the response will only contain data on citations where the
    probability per each sentiment is more than or equal to the specified value`)
            .min(0).max(1).optional().default(0.4),
          internal_list_limit: z.number().min(1).max(20).default(1)
            .describe(
              `maximum number of elements within internal arrays
              you can use this field to limit the number of elements within the following arrays`)
            .optional(),
    
        };
      }
  • Registers the ContentAnalysisSummaryTool instance along with others by mapping tool names to their descriptions, params, and handlers.
    getTools(): Record<string, ToolDefinition> {
      const tools = [
        new ContentAnalysisSearchTool(this.dataForSEOClient),
        new ContentAnalysisSummaryTool(this.dataForSEOClient),
        new ContentAnalysisPhraseTrendsTool(this.dataForSEOClient),
        // Add more tools here
      ];
    
      return tools.reduce((acc, tool) => ({
        ...acc,
        [tool.getName()]: {
          description: tool.getDescription(),
          params: tool.getParams(),
          handler: (params: any) => tool.handle(params),
        },
      }), {});
    }
Behavior1/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. However, it only states what the tool does without revealing any behavioral traits such as whether it's a read-only operation, rate limits, authentication needs, or what the output looks like. For a tool with 7 parameters and no output schema, this lack of transparency is inadequate.

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 a single, efficient sentence that states the tool's function without unnecessary words. It is front-loaded and to the point, though it could be more informative. There is no wasted verbiage, making it concise, but it lacks depth which affects its overall helpfulness.

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 with 7 parameters, nested objects, no annotations, and no output schema, the description is incomplete. It does not explain the return values, behavioral aspects, or how to interpret results. For a tool that likely returns aggregated citation data, more context is needed to guide effective use, making this description insufficient for the tool's complexity.

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?

The schema description coverage is 100%, meaning all parameters are well-documented in the input schema itself. The description does not add any additional meaning or context beyond what the schema provides, such as explaining how parameters interact or typical use cases. Since the schema handles the heavy lifting, a baseline score of 3 is appropriate, as the description neither compensates nor detracts.

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

Purpose2/5

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

The description states 'provide you with an overview of citation data available for the target keyword,' which is a tautology that essentially restates the tool name 'content_analysis_summary.' It lacks a specific verb and resource, and does not differentiate from sibling tools like 'content_analysis_search' or 'content_analysis_phrase_trends.' The purpose is vague and does not clarify what 'citation data' entails or how it differs from other content analysis tools.

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

Usage Guidelines1/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 does not mention any prerequisites, context for usage, or exclusions. With many sibling tools available, such as 'content_analysis_search' and 'content_analysis_phrase_trends,' there is no indication of when this summary tool is preferred over others, leading to potential misuse.

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/ravinwebsurgeon/seo-mcp'

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