Skip to main content
Glama
Sign In

Serpier

by com.serpier
OverviewDiscussionsAdmin

get-seo-page-performance

Read-only

Read stored Lighthouse page-speed results for the project's tracked pages: the latest audit run, recent runs, and per page the latest mobile and desktop scores (0-100) with Core Web Vitals. Read-only; it does not start an audit. Use get-seo-page-performance-detail with a page id for one page's history and fix suggestions. 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-page-performance"
  }
}

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

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, but the description adds value beyond them by clarifying that it 'does not start an audit' — a meaningful distinction from a run-triggering sibling. The explicit failure condition is further useful behavioral context; only the absence of detail on result volume/staleness keeps it from a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three compact sentences: what it returns, the read-only/does-not-audit caveat, the alternative route, and the failure condition. Everything is front-loaded and each clause carries distinct 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 still tells the agent what comes back (latest audit run, recent runs, per-page mobile/desktop scores, Core Web Vitals) and what causes failure. Annotations cover the safety profile, so nothing essential is missing for correct invocation.

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%, so advertiserProjectId, context, and llm_model are fully documented in the schema. The description adds no parameter-level meaning beyond a passing mention of 'page id' for the sibling, so the baseline of 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?

Specific verb and resource: 'Read stored Lighthouse page-speed results' for 'the project's tracked pages', with the exact payload enumerated (latest run, recent runs, per-page mobile/desktop scores 0-100, Core Web Vitals). It is clearly distinguishable from get-seo-page-performance-detail, which is scoped to one page's history.

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?

Names the alternative explicitly and the condition that selects it: 'Use get-seo-page-performance-detail with a page id for one page's history and fix suggestions.' It also states a precondition/failure mode ('Fails when SEO Performance is not set up for the project'), so the agent knows when not to call it.

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