free-seo-mcp

keywords_load

Read-onlyIdempotent

Load saved keywords for a project and language, with optional filtering by tier or cluster, to retrieve organized keyword sets for targeted SEO analysis.

Instructions

Load saved keywords for a project and language, optionally filtered by tier/cluster.

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": {
      "project": "<project>",
      "lang": "<lang>"
    },
    "name": "keywords_load"
  }
}

Input Schema

Name	Required	Description
`lang`	Yes
`tier`	No	Only rows with this tier
`cluster`	No	Only rows with this cluster
`project`	Yes

Output Schema

Name	Required	Description	Default
`path`	Yes
`rows`	Yes
`total`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 25, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the description need not repeat safety traits. It adds value by clarifying the operation is a filtered retrieval of saved keywords, but gives no additional behavior such as pagination, ordering, or empty-result handling. No contradiction with annotations.

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?

A single sentence that front-loads the core action and resource, then appends the optional filter conditions. Every word earns its place with no redundant filler.

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 load operation with an output schema and safety annotations, the description covers purpose and filters adequately. The only material gap is explicit usage guidance versus alternative keyword-generation/save tools, which is not severe enough to lower the score further.

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 coverage is only 50% (tier and cluster have descriptions; project and lang do not), so the description partially compensates by identifying project/lang as the scoping keys and tier/cluster as optional filters. It adds relational meaning but no format or value details 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 a specific verb ('Load') with a clear resource ('saved keywords for a project and language') and specifies optional filters. This differentiates it from key siblings like keywords_save (which saves rather than loads) and suggest/expand tools (which generate rather than retrieve stored data).

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?

The description implies the tool is for retrieving previously saved keywords, so an agent can infer when to use it rather than keywords_save or suggestion tools. However, it offers no explicit when-to-use/when-not-to-use guidance or named alternatives, leaving some routing to inference.

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

Deploy Server