Skip to main content
Glama
Sign In

Keytomic

by com.keytomic.app
OverviewDiscussionsAdmin

Get backlinks

get_backlinks
Read-only

Returns the saved backlink report of a site, the same data as the Backlinks page: the backlinks that point to the site, with the referring page, anchor text, authority (rank, 0 to 100), dofollow, spam score and whether the link is broken or new, and the backlink gaps: pages that link to a competitor but not to the site, with an outreach draft for each. It reads saved data only and never reads new data from DataForSEO. fetchedAt says when the data was read; the Backlinks page reads new data on its first view after nextSyncAt. The gaps come only from competitors whose backlinks are saved; competitorDomains lists the competitors of the gap list. When no report is saved, the result says so and gives backlinksUrl, where the user opens the Backlinks page to read the data. Spends no credits.

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": {
      "projectId": "<projectId>"
    },
    "name": "get_backlinks"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMost saved backlinks to return. truncated is true when the report has more.
projectIdYesSite to act on, from list_sites.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations (readOnly, non-destructive, closed-world), the description discloses zero credit spend, the saved-vs-fresh data distinction, the meaning of fetchedAt versus the page's nextSyncAt refresh, the constraint that gaps only include competitors with saved backlinks, competitorDomains semantics, and the empty-state behavior with a URL. This is unusually rich behavioral context that annotations alone could not supply.

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?

The single dense paragraph is front-loaded with what the tool returns, then moves to data-freshness semantics and the empty case. Almost every sentence carries information the agent needs, though the enumeration of return fields is long and could be split for readability.

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 no output schema, the description fully carries the burden: it describes the returned record fields, the gap/outreach content, competitorDomains, fetchedAt, truncation via limit, and the no-report fallback. Nothing an agent needs in order to call this correctly or interpret its result is 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% and both parameters are fully documented in the schema (projectId sourcing from list_sites, limit with maximum and the truncated flag). The description adds no additional meaning about parameter syntax or interaction, so the 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?

The description opens with a specific verb and resource (returns the saved backlink report of a site) and immediately scopes it ('saved data only, never reads new data from DataForSEO'), which separates it from both the live Backlinks page and any fresh-fetch tool. It even enumerates the content of the return (backlinks, anchor text, authority, dofollow, spam score, gap pages with outreach drafts), so an agent knows exactly what it gets.

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?

It gives clear context for use: this is the read of already-persisted data, and when no report exists the result points to backlinksUrl where the user can trigger a fresh read. That effectively routes the agent away from this tool when fresh data is required, though it never names a sibling tool or states an explicit 'do not use when' clause.

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

All Keytomic 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