Skip to main content
Glama

Visibility Genies

List saved keywords

list_saved_keywords
Read-only

Lists the keywords saved to a project with the volume, difficulty and CPC saved for each, and their tags, newest first. Reads the database only: no data is bought and no credits are used.

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": {
      "projectId": "<projectId>"
    },
    "name": "list_saved_keywords"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagsNoOnly keywords carrying any one of these tags.
limitNoHow many keywords to return. Defaults to 100.
searchNoOnly keywords containing this text.
projectIdYesRequired. The Visibility Genies project this call works in and is billed to. Call list_projects to find one.

Output Schema

NameRequiredDescriptionDefault
metaNo
rowsYes
tagsYes
totalCountYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description does add genuine context beyond them: the ordering (newest first) and the billing fact that no credits are consumed, which matters on this API since a sibling's projectId is described as "billed to." Return-field detail is largely duplicative with the output schema.

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 sentences with no filler; the core action and returned fields come first, and the cost clarification follows as a short, high-value qualifier. Nothing could be removed without losing an agent-relevant fact.

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?

Output schema exists, so return values need no explanation, and annotations carry the read-only profile; the description fills the remaining meaningful gap about credit cost and ordering. It could go further by clarifying filter combination semantics, but for a simple filtered list this is nearly complete.

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 tags, limit, search and projectId are all documented with meaning and constraints, and the schema even routes to list_projects. The description adds nothing about parameter behavior (e.g. how tags and search combine), so baseline 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 specific verb and resource ("Lists the keywords saved to a project") plus the returned fields (volume, difficulty, CPC, tags) and ordering (newest first). It does not explicitly differentiate itself from similar siblings such as get_ranked_keywords or get_saved_keyword_gap, so it stops short of a 5.

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?

Usage is only implied: "saved" paired with "no data is bought and no credits are used" signals this is for reading existing data rather than running new research, but no sibling is named as the alternative and no explicit when-not condition is given. An agent must infer that research_keywords is the other path.

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