Skip to main content
Glama
Sign In
cfp-seo-agent

cfp-seo-agent

by CFP-102
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

keyword_metrics

Idempotent

Retrieve Google Ads search volume, competition, CPC, and 12-month trends for up to 1,000 keywords per call to validate keyword demand and plan SEO or PPC campaigns.

Instructions

Google Ads search volume, competition, CPC and 12-month history for up to 1000 keywords per call (DataForSEO Google Ads Search Volume Live). Returns: JSON with keywords. SANDBOX (development): returns dummy data, no payment.

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": "keyword_metrics"
  }
}

Input Schema

NameRequiredDescriptionDefault
keywordsYesKeywords to look up: 1 to 1000 entries, each up to 80 characters / 10 words. Lowercased, duplicates removed.
language_codeNoLanguage code such as en or de. Default: English if available for the country, else its first language. Unsupported country/language pairs are refused before payment.
location_codeNoDataForSEO location code. Country level: 2840 = United States (default), 2276 = Germany, 2040 = Austria, 2756 = Switzerland. Google SERP, Maps, News, Images and Local Market Check also accept city/region codes in Germany, Austria and Switzerland (free lookup: GET /api/v1/locations?q=...).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false, openWorldHint=true and idempotentHint=true; the description adds genuinely new behavioural context the annotations cannot convey: that this is a Live DataForSEO endpoint and that the sandbox returns dummy data with no payment, which signals that production calls are metered. It does not state rate limits or per-call cost explicitly, keeping it short of a 5.

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?

Three short sentences, front-loaded with the payload and metrics before the source and environment notes. 'Returns: JSON with keywords' is the weakest sentence, adding little beyond the first sentence, but overall it is tight with no padding.

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?

With no output schema, the description does the necessary work by naming the returned metrics in the opening sentence, and it covers the billing/sandbox dimensions that materially affect a paid, open-world lookup. Minor gap: no note on failure/refusal behaviour or result ordering for the batch.

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%, with defaults, patterns, code examples and city/region caveats already documented in the schema. The description only restates the 1000-keyword cap that maxItems already encodes, adding no new meaning about keywords, language_code or location_code.

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 resource and the exact metrics returned (Google Ads search volume, competition, CPC, 12-month history) plus the underlying DataForSEO endpoint, so the agent knows precisely what data it gets. It does not explicitly contrast with near-neighbours like keyword_ideas, keyword_difficulty or traffic_estimate, so sibling differentiation is left to inference.

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?

The 'up to 1000 keywords per call' clause implies batch usage, but there is no explicit when-to-use guidance, no statement of when to prefer keyword_ideas or keyword_difficulty instead, and no prerequisites. The only operational hint is the sandbox note, which is about environment, not tool selection.

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

Deploy Server

Other Tools