Skip to main content
Glama
mrkooblu
by mrkooblu

semrush_backlinks_overview

Read-onlyIdempotent

Retrieve backlinks overview summary stats for a domain, URL, or root domain. Analyze link profile metrics quickly.

Instructions

Get backlinks overview summary stats for a target

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
targetYes
target_typeNoroot_domain
limitNo
Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, so the safety profile is known. However, the description adds no further behavioral context such as what the summary stats contain, data freshness, or pagination, beyond 'summary stats'.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single short sentence but is under-specified, lacking necessary details for effective tool use. Conciseness is achieved at the expense of informativeness.

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

Completeness1/5

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

With 3 parameters, no output schema, and many sibling tools, the description is highly incomplete. It fails to describe what the overview includes, parameter formats, or usage context, leaving an agent underinformed.

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

Parameters1/5

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

Schema description coverage is 0%, with 3 parameters (target, target_type, limit). The description mentions only 'target' but does not explain target_type enum values, limit semantics, or provide any additional parameter meaning.

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 it retrieves overview summary stats for backlinks for a target. The verb 'Get' and resource 'backlinks overview summary stats' are specific, but it does not explicitly distinguish from sibling tools like semrush_backlinks, which may provide more detail.

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 on when to use this tool versus alternatives (e.g., semrush_backlinks, semrush_backlinks_anchors). The description does not mention use cases, prerequisites, or when not to use it.

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/mrkooblu/semrush-mcp'

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