Skip to main content
Glama

Sextant Web - Website GEO, SEO, and Analytics

List saved lookups

research_saved
Read-onlyIdempotent

Paid lookups this site already bought (competitor lookups, backlinks, keyword ideas, SERPs, AI answers, local SEO), newest first: what was looked up, when, by whom and from where. Free. Pass tool (for example seo.get_domain_overview) to list one kind. research_saved_get opens one for free.

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": {
      "siteId": "<siteId>"
    },
    "name": "research_saved"
  }
}

Input Schema

NameRequiredDescriptionDefault
toolNo
limitNo
siteIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior; the description adds useful context about what is returned, newest-first ordering, cost, filtering, and the related open tool. It does not describe pagination or limit behavior beyond what the schema implies.

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 description is compact and front-loads the primary purpose, categories, ordering, and returned attributes. Some phrasing is dense and the fragment 'Free.' is slightly abrupt, but there is little wasted text.

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?

For a read-only list tool with no output schema, it describes the important result fields, ordering, cost, filtering, and the follow-up tool. The main gap is that limit behavior is not covered.

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 0%, and the description compensates well for the tool parameter with an example and filtering purpose. However, siteId is only implied by 'this site' and the limit parameter is not explained.

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 states a specific verb and resource: listing paid lookups saved for a site, including concrete categories and ordering. It clearly distinguishes itself from research_saved_get by explaining that research_saved_get opens one lookup.

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?

It tells the agent to pass the tool parameter to filter to one kind of lookup and directs opening to research_saved_get. It does not explicitly state when to prefer this over other list/log tools, but the core usage guidance is clear.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources