Serpier

get-seo-referring-domains

Read-only

Page through the individual domains linking to the project, from stored backlink data: domain rank, spam score, backlinks, dofollow links, first and last seen, and whether the domain was gained or lost this month. Read-only. Filter, search, and sort to answer questions like which dofollow links were lost; use get-seo-backlink-overview for totals and trends. Returns one page (default 50 rows) and the total count. Fails when SEO Performance is not set up for the project.

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": {
      "advertiserProjectId": "<advertiserProjectId>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "get-seo-referring-domains"
  }
}

Input Schema

Name	Required	Description
`page`	No	1-based page number.
`limit`	No	Results per page (1-100).
`search`	No	Free-text search term; an empty string means no search.
`context`	Yes	Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution."
`filters`	No	Array of filters to apply. Multiple filters are combined with AND logic. To match ANY of several values on the same column, use ONE filter with the 'is any of' operator.
`orderBy`	No	Sort order: objects mapping one column id to 'asc' or 'desc'. Empty uses the list's default order.
`llm_model`	Yes	The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" — never guess.
`advertiserProjectId`	Yes	Project id from get-projects or get-project.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.3/5.0

Behavior4/5

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

Beyond the read-only annotations, the description discloses that data comes from stored backlink data, that results are paginated with a total count, and the setup failure mode. Minor deduction: it does not say whether 'gained/lost this month' is a rolling or calendar month, and the stated page size conflicts with the schema's limit default.

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 tight sentences: purpose first, then use cases and the sibling alternative, then return shape and failure condition. No filler; the only bloat is the redundant 'Read-only' given readOnlyHint.

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 carries the return burden well: it lists the columns, states that one page plus a total count comes back, and names both the paging parameters and the setup precondition. Nothing an agent needs to call it correctly is missing, apart from the page-size discrepancy noted above.

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

Parameters2/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, but the description affirmatively misleads: it says 'Returns one page (default 50 rows)' while the schema defines limit with default 20 and maximum 100. That contradiction pushes it below baseline, since an agent may rely on the wrong default.

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 ('Page through the individual domains linking to the project') and enumerates the returned fields (domain rank, spam score, backlinks, dofollow, first/last seen, gained/lost). It explicitly separates itself from get-seo-backlink-overview, which covers totals and trends.

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

Usage Guidelines5/5

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

Gives a concrete use case ('which dofollow links were lost') and names the alternative with its own scope ('use get-seo-backlink-overview for totals and trends'). It also states the precondition for failure (SEO Performance not set up).

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

All Serpier tools Inspect

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.