Skip to main content
Glama

SEO Rank Fixer

Internal link suggestions

internal_links
Read-onlyIdempotent

Internal link suggestions for one site, built from its Google Search Console data and our read of its pages: pages ranking 4th to 20th for searches with real impressions, and other pages of the same site that already mention the search but do not link to them yet. Each suggestion has the page to add the link on, the page to link to, the link text, the sentence it appears in, why, and a conservative estimate of extra clicks a month. Read-only.

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": {
      "siteId": "<siteId>"
    },
    "name": "internal_links"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteIdYesA site id from list_sites.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile, so the trailing 'Read-only' adds nothing, but the description goes further by disclosing the algorithm (pages ranking 4th-20th with real impressions, existing mentions without links) and the fields returned per suggestion. It stops short of stating freshness, latency, or that a GSC connection is a precondition.

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?

Front-loaded with the purpose, then the selection logic, then the return contents — a sensible order with no filler. The single long sentence with an embedded field list is dense but each clause carries information.

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, the description usefully enumerates what each suggestion contains, including the click estimate, and explains how suggestions are derived. Only minor gaps remain: no mention of result volume, pagination, or the GSC dependency.

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

Parameters3/5

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

Schema coverage is 100% and the single siteId parameter is already documented as coming from list_sites. The description's 'for one site' merely reinforces cardinality, so it adds little beyond the schema — the baseline of 3 applies.

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?

States a specific verb and resource: internal link suggestions for one site, and names the data sources (Search Console plus page reads) and the selection criteria. An agent can distinguish this from broader siblings like opportunities or content_briefs without opening a schema.

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?

The scope ('for one site') implies the use case, and the schema note points to list_sites for obtaining the id. However, there is no explicit statement of when to choose this over opportunities, content_briefs, or write_fix, and no prerequisites such as a Search Console connection being required.

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.