Skip to main content
Glama
ayrank-tools

ayrank-tools

Official
by ay-automate

E-E-A-T trust signals

ayrank_eeat_signals
Read-only

Checks an article URL for 11 E-E-A-T trust signals, showing each as found or missing with evidence so you can identify missing bylines, author links, dates, schema, and contact links.

Instructions

Use to list 11 trust signals an article shows (byline, author page link, Article and Person JSON-LD, published and updated dates, About and Contact links, outbound links), each found or missing with evidence. Google says E-E-A-T is not a ranking factor by itself, so there is a found count and no score. Free AY Rank API, no key. JavaScript is not run, so content added by scripts is not seen.

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": {
      "url": "<url>"
    },
    "name": "ayrank_eeat_signals"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe article to check, like https://example.com/blog/post.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior5/5

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

Beyond readOnlyHint/openWorldHint, it discloses three things annotations cannot: no API key required, no JavaScript execution (so script-injected content is invisible), and that output is a found count rather than a score. The JS limitation is exactly the kind of silent-result caveat an agent needs to avoid misreading missing signals as real absences.

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

Conciseness5/5

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

Front-loaded with the action and resource, then constraint, then expectations about output, then environment limits. The parenthetical enumeration of signals is long but each item is information the agent would otherwise have to discover from a call.

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 correctly takes on the job of describing return shape (each signal found or missing with evidence, plus a found count) and call preconditions (free, no key). It is nearly complete; only the response container or field naming is left unspecified, which is minor for a single-URL read 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% and the url parameter carries its own example, so the schema does the heavy lifting. The description adds only indirect meaning by framing the input as "an article", which matches the schema's example URL; no additional format or validation semantics are supplied.

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?

Specific verb (list) plus a precisely scoped resource (11 E-E-A-T trust signals on an article), with the signals enumerated so an agent knows exactly what comes back. The explicit note that there is a found count and no score distinguishes it from scoring siblings such as ayrank_title_score without needing to name them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Use to list..." plus the enumeration gives a clear condition for selection, and the "no score" clarification implicitly tells the agent not to reach for this tool when a graded score is wanted. It stops short of naming an explicit alternative or a when-not-to-use case, so it falls just below the top band.

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