Skip to main content
Glama

BRAINIAC Content & Keyword Analytics

Internal link suggestions

seo-content_internal-link-suggest
Read-onlyIdempotent

Suggest internal links by unigram TF-IDF cosine similarity and extract exact or partial anchor text from target keywords. Price $0.04 USDC. POST /api/v1/seo-content/internal-link-suggest. An unpaid call returns the x402 payment terms and does not run.

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": {
      "pages": "<pages>"
    },
    "name": "seo-content_internal-link-suggest"
  }
}

Input Schema

NameRequiredDescriptionDefault
pagesYespages, array. Required.
maxPerSourceNomaxPerSource, integer, from 1 to 50. Required.
existingLinksNoexistingLinks, array. Required.
minSimilarityNominSimilarity, number, from 0 to 1. Required.

Output Schema

NameRequiredDescriptionDefault
sourcesNosources. Array.
limitationsNolimitations. Array.
suggestionsNosuggestions. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds materially new behavior: a $0.04 USDC price, the POST endpoint, and the x402 failure mode where an unpaid call returns payment terms without executing — exactly the operational detail an agent needs before spending money.

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?

Three compact sentences, front-loaded with the capability, then cost, then payment behavior. The raw 'POST /api/v1/seo-content/internal-link-suggest' line is the least load-bearing for an MCP agent and borders on redundant, but nothing is padded or buried.

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 an output schema present and full parameter coverage in the schema, the description only needs to carry mechanism and operational constraints — which it does, including the critical payment gate. The one remaining gap is any hint about input scale or expected result shape (e.g., number of pages to submit) for a batch-oriented tool.

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 description coverage is 100%, so the schema itself documents pages, maxPerSource, existingLinks and minSimilarity. The description only obliquely touches parameters by mentioning 'target keywords' and 'anchor text'; it adds no format, ordering, or semantics for existingLinks pairs or similarity thresholds beyond what the schema states. Baseline 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 ('Suggest internal links') and goes further to name the mechanism ('unigram TF-IDF cosine similarity') and the anchor-text extraction behavior. No sibling in the supplied list offers link suggestion, so the agent can identify this tool's job immediately.

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?

Usage is implied by the algorithmic description and the target-keyword framing, and the payment sentence tells the agent a call has a cost and what happens if unpaid. However, there is no explicit when-to-use or when-not-to-use guidance, and no routing to related tools such as near-duplicate or topic-coverage utilities.

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.

Resources