Serpier

get-seo-backlink-overview

Read-only

Read the project's backlink profile over time from stored monthly snapshots (up to 24 months): domain rating, backlinks, and referring domains per snapshot, the latest full snapshot, recently gained and lost referring domains, and the latest domain rating of rival domains. Read-only. snapshotPending is true before the first snapshot. Use get-seo-referring-domains to list and filter individual referring domains. 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-backlink-overview"
  }
}

Input Schema

Name	Required	Description
`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."
`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.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and destructiveHint=false, so 'Read-only' adds nothing; however the description contributes real behavioral context the annotations do not: a 24-month snapshot window, the snapshotPending flag being true before the first snapshot, and a hard failure mode when SEO Performance is unconfigured. Missing only lower-value details such as response ordering or snapshot granularity beyond 'monthly'.

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 the core read operation and returned data, then alternative routing, then the failure condition — a sensible order. Slightly padded by 'Read-only', which merely restates the readOnlyHint annotation, but the remaining sentences each carry information.

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 burden of describing returns and does so by enumerating each component of the payload, plus the time window and the pending-snapshot sentinel. For a read-only, three-parameter tool this covers everything an agent needs before calling it.

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 all three parameters are documented in the schema, including advertiserProjectId's source (get-projects/get-project). The description only implicitly references the project; it adds no new meaning about context or llm_model, 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?

States a specific verb and resource ('Read the project's backlink profile over time') and enumerates exactly what the result contains: domain rating, backlinks, referring domains per snapshot, latest full snapshot, gained/lost referring domains, and rival domain ratings. It also names the sibling it is not (get-seo-referring-domains), so an agent can separate it from get-seo-overview and get-seo-competitor-detail without opening schemas.

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?

Explicitly routes the agent to get-seo-referring-domains when the goal is listing or filtering individual referring domains, which is the primary confusion risk for this tool family. It also states a precondition ('Fails when SEO Performance is not set up for the project'), giving a concrete when-not-usable condition.

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.