Skip to main content
Glama

Honeyfield Marketing MCP

DataForSEO: Related keywords

dfs_related_keywords
Read-only

Verwandte Keywords zu einem Seed mit Search Volume + CPC. location/language: Default aus dem Workspace; Format wie bei dfs_keyword_volume. Fehler kommen als Ein-Element-Liste [{error, ...}] (api_error/task_error, dfs_timeout, dfs_unreachable) — vor der Auswertung auf 'error' pruefen. workspace: Slug des Kunden-Workspace (optional bei nur einem Workspace).

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": {
      "seed_keyword": "<seed_keyword>"
    },
    "name": "dfs_related_keywords"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
languageNo
locationNo
workspaceNo
seed_keywordYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld, and the description adds genuinely useful behavior beyond that: errors are returned as a one-element list containing an 'error' object with specific types (api_error/task_error, dfs_timeout, dfs_unreachable), with an instruction to check for 'error' before evaluating. That is exactly the kind of non-obvious runtime behavior 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?

Front-loads the core purpose in the first sentence, then tacks on scoping defaults, the error-handling note, and workspace semantics. Compact and largely waste-free, though it could be marginally tighter.

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?

An output schema exists so return values needn't be explained, and the description still covers the important call-time concerns (defaults, error shapes, workspace scoping). For an open-world read tool this is nearly complete; only the limit parameter's behavior is unaddressed.

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 description coverage is 0%, so the description must carry parameter meaning. It explains that location/language default from the workspace and share the format of dfs_keyword_volume, and that workspace is a slug optional when only one workspace exists – covering most parameters well. The 'limit' parameter is left unexplained, keeping it short of a 5.

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 action (fetch related keywords for a seed) plus the metrics returned (Search Volume + CPC), which clearly tells an agent what the tool produces. It implicitly distinguishes itself from sibling research tools (keyword_ideas, keyword_suggestions) by naming 'related keywords' and referencing dfs_keyword_volume for format, though it never explicitly contrasts the siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives defaults and error handling but never says when to reach for this tool versus dfs_keyword_suggestions, dfs_keyword_ideas_for_domain, or dfs_keyword_overview. An agent still has to infer the selection criteria from the name alone.

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