Skip to main content
Glama

ADS Beast

seo_internal_links_audit

Read-only

Orphan and weakly linked pages with the internal links to add. 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_internal_links_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesDomain without scheme.
client_idNo
key_pagesNoKey pages, comma-separated.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/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 safety and external-dependency behavior are covered. The description adds one genuinely non-annotated fact, the 'AI: 1 AI request' cost, which is useful for budgeting, but says nothing about crawl scope, results limit, or whether link recommendations are advisory only.

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

Conciseness3/5

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

It is short and front-loaded, with no filler, which is good. However the phrasing is telegraphic ('Orphan and weakly linked pages with the internal links to add'), and the cost note is bolted on as a separate fragment rather than integrated, so brevity comes at the cost of readability.

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

Completeness2/5

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

With no output schema, the description must frame the result, and it only hints at it ('pages ... with the internal links to add') without saying what fields or format come back per page. For a three-parameter, open-world audit with an AI-cost implication, scope, credit semantics, and return shape are all missing.

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 description coverage is 67%: 'domain' and 'key_pages' are documented in the schema, but 'client_id' has no description anywhere. The description mentions no parameters at all, so it adds zero meaning beyond the schema and does not compensate for the undocumented client_id.

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 'Orphan and weakly linked pages with the internal links to add' conveys the resource analyzed (orphan/weakly linked pages) and the deliverable (suggested links), so an agent can roughly identify the audit. But it is a noun phrase without a verb and never states it is an internal-link audit of a domain, leaving the purpose inferable rather than explicit.

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?

There is no when-to-use guidance, no prerequisites, and no mention of when to pick this over sibling SEO audits such as seo_on_page_audit or seo_technical_audit, even though link structure overlaps both. Usage must be guessed from the name.

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.