Skip to main content
Glama

AEORank — SEO, AEO & GEO Audit Engine

Search Open Knowledge Hub Playbooks

search_knowledge_playbooks
Read-onlyIdempotent

Search peer-reviewed Technical SEO, AEO, and GEO engineering guides from the AEORank Open Knowledge Hub (/learn and /tri-thuc).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_knowledge_playbooks"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage ('en' or 'vi').
queryNoSearch keyword (e.g. RAG, llms.txt, Schema, E-E-A-T, Core Web Vitals).

Output Schema

NameRequiredDescriptionDefault
countYes
playbooksYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description usefully confirms the corpus is bounded to /learn and /tri-thuc and is peer-reviewed, but it does not say what happens when query is omitted (both params are optional), whether results are ranked or paginated, or how large the corpus is.

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?

A single front-loaded sentence led by the verb, with no filler or repetition. It is dense and scannable, though it is a flat sentence with no structure for the optional parameters.

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 annotations covering safety, the description only needs to establish what is searched and from where, which it does. The remaining gap is operational detail about omitting query and result limits, which is minor for a two-parameter search tool.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description earns a notch by characterizing the content the query indexes (technical SEO/AEO/GEO guides) and by pairing the two source paths with the en/vi language dimension, hinting that /tri-thuc serves Vietnamese content. It does not explain the empty-query behavior or result-limit semantics.

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

Purpose4/5

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

States a specific verb ("Search") plus a specific resource (peer-reviewed Technical SEO/AEO/GEO engineering guides) and names the source collections (/learn and /tri-thuc). It is distinguishable from siblings such as lookup_rule or run_sandbox_audit by being a keyword search over a curated guide corpus, though no sibling is named explicitly.

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 content area and source hub imply when to reach for it: finding conceptual or best-practice guidance rather than executing audits or patches. However, there is no explicit when-to-use, when-not, or routing to alternatives (e.g. lookup_rule for a specific rule), leaving the agent to infer the boundary.

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.