Skip to main content
Glama

ADS Beast

seo_backlink_analysis

Read-only

Backlink profile quality, toxic links and link-building opportunities. AI: 1 AI request.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "domain": "<domain>"
    },
    "name": "seo_backlink_analysis"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesDomain without scheme.
client_idNo
competitorsNoCompetitor domains, comma-separated.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds one genuinely useful non-annotation fact – the cost ('1 AI request') – but says nothing about output shape, data freshness, depth of crawl, or failure modes for an open-world tool that hits external sources.

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?

Two short sentences, front-loaded with the capability and closing with the cost signal – nothing is padded. It is arguably over-terse rather than verbose, but every sentence present earns its place.

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?

For a read-only, three-parameter tool with no output schema, the definition is minimally adequate: the agent knows it analyzes backlinks and costs one AI request. It is not complete, though – the return values, the meaning of client_id, and the boundary against sibling SEO tools are left unaddressed.

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

Parameters2/5

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

Schema coverage is 67%: domain and competitors are documented in the schema, but client_id has no description anywhere. The description adds zero parameter meaning, so it fails to compensate for the undocumented parameter or to clarify formats such as comma-separated competitor lists.

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

Purpose3/5

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

The fragment names the resource and three sub-analyses (profile quality, toxic links, link-building opportunities), so the general purpose is inferable. However, there is no verb and no differentiation from overlapping siblings such as seo_domain_authority_audit or seo_internal_links_audit, so an agent cannot tell which backlink-flavoured tool to pick from the name and text alone.

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 contains no when-to-use guidance, no prerequisites (e.g. that a domain is required, that competitors are optional), and no mention of alternatives. The only contextual hint is the cost note, which is not usage guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.