Skip to main content
Glama
Sign In

grounded-aeo

by com.groundedaeo
OverviewDiscussionsAdmin

get_competitive_snapshot

Get the latest competitive intelligence for a cataloged domain: the owner's most recent ranking-footprint snapshot, the AI-prompt vs Google demand table for its watched keywords, and each tracked competitor with their own latest snapshot. Read-only. Only domains whose owner has claimed them are exposed; anything else returns found:false. Counts are ranking FOOTPRINT, never traffic, and every volume is a modelled estimate. A null means no estimate has been collected, never zero.

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": {
      "domain": "<domain>"
    },
    "name": "get_competitive_snapshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesCompany domain, e.g. acme.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden. It explicitly discloses read-only behavior, the found:false edge case for unclaimed domains, that counts are ranking footprint (not traffic), that volumes are modelled estimates, and that null means no estimate (not zero). This is exemplary behavioral disclosure.

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?

Each sentence earns its place: the first defines the main purpose, and the rest add distinct clarifying details (read-only, eligibility, data semantics, null meaning). It is well-structured and front-loaded, with no redundant content.

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?

Despite having only one parameter, no output schema, and no annotations, the description fully covers what the tool returns, under what conditions it returns found:false, and how to interpret the data. For this complexity level, it is complete and self-sufficient.

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

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema describes 'domain' simply as a company domain with an example. The description adds the essential semantics that the domain must be cataloged and claimed, which is critical for interpreting returned data. This goes beyond the schema's basic definition.

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?

The description opens with 'Get the latest competitive intelligence for a cataloged domain' and then enumerates the exact components returned: the owner's ranking-footprint snapshot, the AI-prompt vs Google demand table, and tracked competitors' snapshots. This is a specific verb+resource that clearly distinguishes it from sibling tools like get_company_facts or get_engine_visibility.

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

Usage Guidelines4/5

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

The description provides clear eligibility conditions ('Only domains whose owner has claimed them are exposed; anything else returns found:false') and notes the read-only nature, which helps an agent decide when to call it. However, it does not explicitly mention alternatives or compare to sibling tools, so it stops short of full guidance.

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

All grounded-aeo 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