Skip to main content
Glama
Sign In

Serpier

by com.serpier
OverviewDiscussionsAdmin

get-seo-competitor-detail

Read-only

Head-to-head stats and tracked-keyword gap for one rival domain. Free — uses stored run data only.

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>",
      "competitorDomain": "<competitorDomain>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "get-seo-competitor-detail"
  }
}

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.
competitorDomainYesCompetitor domain from get-seo-competitors, e.g. example.com.
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 declare readOnlyHint=true, openWorldHint=false, destructiveHint=false, so safety is covered. The description adds genuinely new behavioral context: the result is computed from stored run data and costs nothing, which tells the agent results may reflect a prior run rather than live data. It does not cover what happens when the domain has no stored data or no tracked keywords.

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?

Two short sentences, zero filler, with the core purpose front-loaded and the cost/staleness caveat trailing as a qualifier. Nothing could be removed without losing information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 'head-to-head stats and tracked-keyword gap' is only a label rather than a description of the shape or fields returned. It is adequate for an agent to decide to call it, but thin on what to expect back or on empty/edge-case behavior.

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 each parameter already documents its source (competitorDomain from get-seo-competitors, advertiserProjectId from get-projects). The description adds no further constraint or format detail beyond the schema, so the baseline of 3 applies.

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?

States a concrete resource ('one rival domain') and the specific outputs ('head-to-head stats and tracked-keyword gap'), which reads distinctly from the list-oriented get-seo-competitors and the single-keyword get-seo-keyword-detail. It stops short of naming a sibling explicitly, so the differentiation is inferable rather than stated.

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?

'Free — uses stored run data only' implies when this is appropriate (cheap, cached follow-up analysis rather than a fresh pull), and the competitorDomain parameter points back to get-seo-competitors. However, there is no explicit when/when-not guidance against alternatives such as get-seo-keyword-detail or get-seo-overview, so the agent must infer the routing itself.

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