Skip to main content
Glama
cortex8

DataForSEO MCP Server

by cortex8

backlinks_competitors

Identify websites competing for backlinks by analyzing shared link profiles and intersection counts to reveal strategic opportunities.

Instructions

This endpoint will provide you with a list of competitors that share some part of the backlink profile with a target website, along with a number of backlink intersections and the rank of every competing website

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
exclude_internal_backlinksNoindicates if internal backlinks from subdomains to the target will be excluded from the results if set to true, the results will not include data on internal backlinks from subdomains of the same domain as target if set to false, internal links will be included in the results
exclude_large_domainsNoindicates whether large domain will appear in results if set to true, the results from the large domain (google.com, amazon.com, etc.) will be omitted
filtersNoarray of results filtering parameters optional field 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, ilike, not_ilike, match, not_match you can use the % operator with like and not_like to match any string of zero or more characters example: ["rank",">","100"] [["target","like","%forbes%"], "and", [["rank",">","100"],"or",["intersections",">","5"]]]
limitNothe maximum number of returned domains
main_domainNoindicates if only main domain of the target will be included in the search if set to true, only the main domain will be included in search
offsetNooffset in the results array of returned networks optional field default value: 0 if you specify the 10 value, the first ten domains in the results array will be omitted and the data will be provided for the successive pages
order_byNoresults sorting rules optional field you can use the same values as in the filters array to sort the results possible sorting types: asc – results will be sorted in the ascending order desc – results will be sorted in the descending order you should use a comma to set up a sorting type example: ["rank,desc"] note that you can set no more than three sorting rules in a single request you should use a comma to separate several sorting rules example: ["intersections,desc","rank,asc"]
targetYesdomain, subdomain or webpage to get backlinks for required field a domain or a subdomain should be specified without https:// and www. a page should be specified with absolute URL (including http:// or https://)
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the tool 'will provide you with a list' but lacks details on rate limits, authentication needs, error handling, pagination (beyond offset/limit parameters), or data freshness. For a tool with 8 parameters and no output schema, this is insufficient to inform the agent about operational behavior.

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, well-structured sentence that efficiently conveys the core functionality. It avoids redundancy and is front-loaded with key information. However, it could be slightly more concise by integrating output details more seamlessly, but it remains highly efficient with no wasted words.

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 (8 parameters, no annotations, no output schema), the description is minimally adequate. It clarifies the purpose but lacks usage guidelines, behavioral context, and output details (e.g., format of 'list of competitors'). While the schema covers inputs well, the description does not compensate for missing annotations or output schema, leaving gaps in overall 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?

The description adds no parameter-specific semantics beyond what the input schema provides. Since schema description coverage is 100%, the schema fully documents all 8 parameters (e.g., target, filters, limit). The description's mention of 'backlink intersections' and 'rank' relates to outputs, not inputs, so it does not enhance parameter understanding. This meets the baseline for high schema coverage.

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?

The description clearly states the tool's purpose: 'provide you with a list of competitors that share some part of the backlink profile with a target website, along with a number of backlink intersections and the rank of every competing website.' It specifies the verb ('provide'), resource ('list of competitors'), and key outputs ('backlink intersections,' 'rank'), distinguishing it from sibling tools like backlinks_backlinks or backlinks_summary which focus on different backlink aspects.

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 does not mention sibling tools like backlinks_domain_intersection or backlinks_page_intersection, which might offer similar intersection analysis, nor does it specify prerequisites, exclusions, or contextual cues for selection. This leaves the agent without direction on tool choice.

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/cortex8/oyt-dataforseo-mcp-worker'

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