semrush_backlinks
Retrieve backlinks for any domain or URL to analyze link profiles and identify linking domains.
Instructions
Get backlinks for a specific domain or URL
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| target | Yes | ||
| limit | No |
Retrieve backlinks for any domain or URL to analyze link profiles and identify linking domains.
Get backlinks for a specific domain or URL
| Name | Required | Description | Default |
|---|---|---|---|
| target | Yes | ||
| limit | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Description adds no behavioral context beyond what annotations already declare (readOnly, idempotent). No mention of data freshness, limits, or response format.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Single sentence is concise but too brief to be useful; lacks essential details about usage.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
No output schema or description of return value, leaving the agent uninformed about what the tool returns.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema has 0% description coverage and description does not explain 'target' format or 'limit' behavior, leaving parameters ambiguous.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states the tool gets backlinks for a domain or URL, distinguishing it from other backlinks tools that focus on anchors, categories, etc.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool over sibling backlinks tools like semrush_backlinks_anchors or semrush_backlinks_pages.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
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