Skip to main content
Glama

Sextant Web - Website GEO, SEO, and Analytics

List saved keywords

seo_list_saved_keywords
Read-onlyIdempotent

Lists keywords saved to a project (with cached metrics like search volume, difficulty, CPC, and tags if available). Uses no credits — reads from Sextant's database, no DataForSEO call. Each row includes its saved-keyword ID for seo.remove_saved_keywords. Use tag filters when the user asks for a saved segment; multiple tags match ANY tag.

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": "seo_list_saved_keywords"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagsNoOptional tag-name filters. Multiple tags match ANY tag.
limitNoMaximum rows to return, 1 to 250. Defaults to 100.
searchNoOptional keyword text filter.
siteIdYesThe Sextant site ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Adds real behavioral context beyond the readOnly/idempotent annotations: no credits are consumed, no external DataForSEO call is made, metrics are cached and only present 'if available', and tags use ANY-match semantics. This tells the agent about cost and possible data gaps that annotations cannot express.

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?

Four short sentences, front-loaded with what the tool returns and the no-credit guarantee before the filter hint. Minor redundancy from repeating the ANY-tag rule that also appears in the schema.

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 usefully sketches row contents (metrics plus saved-keyword ID) and the cost model. It stops short of describing ordering, pagination, or total counts, which are minor gaps for a 4-parameter list tool.

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 the schema already documents tags, limit, search, and siteId. The description restates the ANY-match tag behavior (already in the schema) and adds nothing about limit defaults, search matching rules, or siteId scope, 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?

States a specific verb and resource ('Lists keywords saved to a project') plus the row contents (cached metrics such as search volume, difficulty, CPC, tags). It also distinguishes itself from DataForSEO-backed siblings by noting it reads Sextant's database, so an agent can tell it apart from sibling list/get tools.

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?

Gives explicit context: use tag filters when the user asks for a saved segment, and names seo.remove_saved_keywords as the follow-up consumer of returned IDs. It does not explicitly state when NOT to use this versus other keyword tools, which keeps it below a 5.

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