Skip to main content
Glama

seo_list_keywords

List and audit your brand's SEO keywords with filters for intent, source, volume, difficulty, tags, and more, plus pagination for large sets.

Instructions

List generated keywords for the brand. Useful for auditing between steps. Returns short detail by default: {id, keyword, intent} per keyword. Use detail="medium" for the full compact summary (priority, searchVolume, difficulty, relevance, clusterId, excludedFromClustering, userTags) or detail="full" for raw keyword objects. Supports server-side filtering: source, intent, clusterId, q (substring search), hasTag, volumeMin/volumeMax, kdMin/kdMax, relevanceMin/relevanceMax, priorityMin/priorityMax, includeDeleted, excludedFromClustering. hasTag filters on userTags (OR match) — use it to find geo-tagged keywords after seo_tag_geography, e.g. hasTag="geo:us-mn" or hasTag="geo:us-mn,geo:us-tx" for multiple regions. Use cursor (from a previous call's response) to page through results beyond limit.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoSubstring search over the keyword text
kdMaxNoMaximum keyword difficulty (inclusive)
kdMinNoMinimum keyword difficulty (inclusive)
limitNo
cursorNoPagination cursor from a previous seo_list_keywords call
detailNoVerbosity of returned item(s): "short" = id + primary label + status (cheap list scan); "medium" = key summary fields + counts (a useful glance); "full" = the complete object. Default "short". Lists default to "short" — to zoom into one item, call its get/view tool with detail="medium" or "full".short
hasTagNoCSV of userTags to filter by (OR match), e.g. "geo:us-mn" or "geo:us-mn,geo:us-tx"
intentNoCSV of search-intent labels to filter by (informational, commercial, navigational, transactional)
sourceNoCSV of keyword sources to filter by (e.g. "seed,expanded")
brandIdNoBrand ID (defaults to active brand)
clusterIdNoFilter by cluster ID, or "none" for unclustered, or "any" for any clustered keyword
volumeMaxNoMaximum search volume (inclusive)
volumeMinNoMinimum search volume (inclusive)
priorityMaxNoMaximum priority score in [0,1] (inclusive)
priorityMinNoMinimum priority score in [0,1] (inclusive)
relevanceMaxNoMaximum relevance score in [0,1] (inclusive)
relevanceMinNoMinimum relevance score in [0,1] (inclusive)
includeDeletedNoInclude soft-deleted keywords (default: excluded)
excludedFromClusteringNoFilter to keywords with this excludedFromClustering value
Behavior5/5

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

With no annotations, the description carries the full burden and does so thoroughly: it discloses default return detail, exact fields per detail level, server-side filtering, hasTag OR-match semantics, includeDeleted default exclusion, and cursor pagination. This gives the agent a complete behavioral model.

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 dense but efficient, with each sentence adding functional value: purpose, detail levels, filter list, hasTag semantics, and pagination. It could be better structured with bullet points, but there is no fluff or redundancy.

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?

For a high-complexity list tool with no output schema and no annotations, this description covers purpose, output shape per detail level, filters, hasTag behavior, and pagination sufficiently. An agent can correctly select and invoke the tool without additional context.

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?

Schema coverage is 95%, so the baseline is 3. The description adds meaningful context by clarifying hasTag as a CSV OR-match with geo-tagging examples, explaining detail verbosity values, and describing cursor-based paging beyond the schema.

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 uses the specific verb 'List' targeting 'generated keywords for the brand', clearly defining the tool's scope. It also distinguishes itself by specifying default return fields and detail levels, making it unambiguous among sibling SEO 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?

It states the tool is 'useful for auditing between steps' and provides guidance on detail levels and pagination. It also advises calling a get/view tool for zooming into an item, but does not explicitly contrast with the sibling seo_list_keyword_ids tool.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/bitsandtea/postking-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server