Skip to main content
Glama
Sign In

Serpier

by com.serpier
OverviewDiscussionsAdmin

get-seo-overview

Read-only

SEO Performance dashboard for a project: config (null when SEO Performance is not set up), keyword quota, latest rank check, movers, ranking bands, SERP and AI Overview stats, credit usage, refreshQuote.credits for an on-demand check, 28-day Search Console traffic, authority, and page speed. Setup happens in the Serpier app under SEO Performance and needs a paid plan.

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-overview"
  }
}

Input Schema

NameRequiredDescriptionDefault
contextYesExplain 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_modelYesThe 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.
advertiserProjectIdYesProject id from get-projects or get-project.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint=true, destructiveHint=false, openWorldHint=false), so the bar is lower, and the description adds real behavior beyond them: the nullable config field signals a not-set-up state rather than an error, the paid-plan prerequisite flags a common failure mode, and 'refreshQuote.credits for an on-demand check' discloses the cost of triggering a refresh. It stops short of describing error shapes or how fresh the cached data is.

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 purpose is front-loaded in the opening clause and the two sentences contain no filler. The long comma-separated inventory of sections is dense but each item maps to a distinct part of the response, so it earns its space; a bulleted or grouped structure would read better than the run-on list.

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 has the full burden of conveying return content, and it does so by enumerating the dashboard sections, plus it flags the null-config prerequisite and the credit cost of an on-demand refresh. What remains thin is the response shape (flat object vs. nested sections) and whether sections can be individually absent, which an agent planning follow-up calls would want to know.

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 the analytics-only context and llm_model fields, so the schema carries the burden. The description only implies that 'a project' corresponds to advertiserProjectId and adds no format or sourcing detail beyond what the schema already says.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states this is an 'SEO Performance dashboard for a project' and enumerates the sections returned (keyword quota, rank check, movers, ranking bands, SERP/AI Overview stats, credit usage, GSC traffic, authority, page speed), which lets an agent distinguish it from narrower siblings like get-seo-keywords or get-seo-backlink-overview. It lacks an explicit action verb (e.g. 'retrieve'), and the phrase 'config (null when SEO Performance is not set up)' is slightly cryptic without context.

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

Usage Guidelines3/5

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

The prerequisite note — setup happens in the Serpier app under SEO Performance and requires a paid plan — is genuinely useful context for when this tool will produce data. However, there is no explicit guidance on when to choose this overview versus drilling into the many sibling detail tools, and no statement that it should be called first to orient before fetching detail.

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

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