Skip to main content
Glama

Honeyfield Marketing MCP

DataForSEO: Keyword trends

dfs_keyword_trends
Read-only

Google-Trends-Verlauf (relative Popularitaet 0-100) fuer bis zu 5 Keywords im selben Zeitfenster — Saisonalitaet, Trend-Vergleich. Max 5 Keywords. time_range: 'past_hour' | 'past_4_hours' | 'past_day' | 'past_7_days' | 'past_30_days' | 'past_90_days' | 'past_12_months' | 'past_5_years' (Default past_12_months). Rueckgabe: series[]{keyword, points[]{date, value}}, averages{keyword: Mittelwert}. location/language: Default aus dem Workspace; Format wie bei dfs_keyword_volume. 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": {
      "keywords": "<keywords>"
    },
    "name": "dfs_keyword_trends"
  }
}

Input Schema

NameRequiredDescriptionDefault
keywordsYes
languageNo
locationNo
workspaceNo
time_rangeNopast_12_months

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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 openWorldHint=true, so the safety profile is covered. The description adds real value by clarifying that values are Google-Trends *relative* popularity (0-100) rather than absolute volume, plus the 5-keyword cap and workspace-defaulting behavior. It says nothing about cost/quota of the external DataForSEO call or failure behavior for invalid keywords.

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-loaded with purpose and value, then constraints, then defaults. The explicit return-shape enumeration (series[]/averages{}) duplicates the available output schema and is the one part that does not earn its space; the long time_range list is justified because the schema carries no enum.

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?

A read-only research tool with an output schema, rich annotations, and five parameters whose semantics are all addressed at least in outline. The only remaining gap an agent would hit in practice is the concrete location/language format, which is outsourced to a sibling tool rather than stated.

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?

With 0% schema description coverage the description carries the full burden and mostly delivers: it enumerates every time_range value with its default, states the 5-item limit on keywords, explains workspace as optional when only one exists, and notes location/language default from the workspace. It falls short only on the concrete format of location/language, deferring to 'Format wie bei dfs_keyword_volume', which forces a lookup in another tool.

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: a Google-Trends trajectory (relative popularity 0-100) for up to 5 keywords within one time window, framed around seasonality and trend comparison. This is distinguishable from volume/idea siblings by the 'Verlauf' (time series) framing, though no sibling is explicitly named as the alternative.

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 clear use contexts (Saisonalität, Trend-Vergleich) and a hard constraint (max 5 keywords) that shapes invocation. It stops short of naming when NOT to use it or pointing to dfs_keyword_volume/dfs_keyword_ideas_for_domain as alternatives for absolute volume or discovery.

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