Skip to main content
Glama

Semrush

by io.github.pipeworx-io

Backlinks Overview

backlinks_overview
Read-onlyIdempotent

Backlinks summary for a domain or URL (Semrush type=backlinks_overview). Returns parsed rows with columns: target, target_type, total (total backlinks), domains_num (referring domains), urls_num (referring URLs), ips_num (referring IPs), follows_num (dofollow), nofollows_num, texts_num, images_num, score (authority score). Note: backlinks reports are not regional — there is no database param. Consumes your Semrush API units.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
targetYesDomain or URL to analyze, e.g. "apple.com".
_apiKeyYesYour own Semrush API key (BYO). Passed to Semrush as the `key` query param. Consumes your Semrush API units.
target_typeNoOne of "root_domain", "domain" (subdomain), or "url". Default root_domain.

TDQS

A4.1/5.0
Behavior4/5

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

Annotations declare readOnly, idempotent, non-destructive. Description adds that it consumes Semrush API units and that backlinks reports are not regional, providing useful behavioral context beyond annotations.

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?

Single paragraph efficiently conveys purpose, return format, and key notes. No filler, but could be slightly more structured with bullet points.

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

Completeness4/5

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

With no output schema, description explains return columns and API unit consumption, covering essential context. Adequate for the tool's simplicity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with clear parameter descriptions. Description adds meaning by listing response columns and clarifying default target_type, which supplements the schema.

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?

Clearly states it returns a backlinks summary for a domain or URL, listing specific columns. Distinct from siblings like domain_organic_keywords or domain_overview.

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

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Implies usage for backlinks overview, mentions absence of regional parameter and API unit consumption, but does not explicitly state when to use vs alternatives or when not to use.

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

All Semrush toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation4/5

Most tools have clearly distinct purposes, but there is some overlap: ask_pipeworx and ask_pipeworx_grounded are very similar, and the multiple Polymarket tools could be confused. The memory tools (remember, recall, forget) are distinct.

Naming Consistency3/5

Tool names consistently use snake_case, but the pattern is not strictly verb_noun. Some names are descriptive phrases (e.g., scan_competitor_ai_presence), while others are straightforward (e.g., keyword_overview). Overall readable but not highly consistent.

Tool Count3/5

32 tools is on the high side for a single server, but the scope is broad (SEO, finance, FDA, betting, memory). The tool count feels slightly excessive, yet each tool appears justified by its specific use case.

Completeness4/5

The tool set covers a wide range of business research needs: SEO, SEC filings, FDA data, betting analytics, and memory. Minor gaps exist (e.g., no direct social media or HR data), but the coverage is impressive for a general-purpose data server.

Resources