Skip to main content
Glama
Sign In

CrunchJunkie

by io.crunchjunkie.app
OverviewDiscussionsAdmin

get_link_anchors

Read-only

The anchor texts of the links DataForSEO found to a client's site, from the STORED answer (no new request, no charge): referring domains, nofollow domains, backlinks, first seen and spam score per anchor, and OUR class (brand, url, generic, descriptive, empty — a heuristic from the client's name and domain, never DataForSEO's). With no stored answer it says so.

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": {
      "clientId": "<clientId>"
    },
    "name": "get_link_anchors"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoRows returned, default 50.
domainNoDomain to read. Default: the client's own.
clientIdYesClient id (from list_clients).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the readOnly/non-destructive annotations, it discloses cost behaviour (no charge), the absence of an upstream request, the empty-state behaviour ('with no stored answer it says so'), and the provenance of the class field as an internal heuristic rather than the vendor's. That is substantial behavioural context the annotations do not cover.

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 what the tool returns and its source, then the per-anchor fields, then the empty-state clause. It is a dense single sentence with nested parentheticals, but every element adds information and nothing is redundant.

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

Completeness5/5

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

With only three parameters and no output schema, the description carries the return-shape burden and does so by enumerating the per-anchor fields and the class taxonomy. It also covers the no-data case, leaving nothing an agent needs missing.

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%, with limit and domain defaults already documented in the schema, so the baseline applies. The description adds meaning about the returned row contents rather than about the three input parameters themselves, so it does not push past the baseline.

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 ('anchor texts of the links ... to a client's site') plus its data source, which separates it from fresh-lookup siblings like run_link_lookup. An agent can tell this is a read of already-collected anchor data without opening the schema.

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?

Gives a clear selection context: STORED answer, 'no new request, no charge', which implies the alternative is a paid fresh lookup. It does not explicitly name run_link_lookup or state when that alternative is required, so it lacks the explicit exclusion an ideal definition would carry.

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

All CrunchJunkie toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources