Mark

Check Keyword Audience

check_keyword_audience

Looks at who currently ranks for a keyword, to judge whether its searchers match your audience. Each call is 1 search: it fetches the current Google top 10. Each call spends provider calls. Pass a savedKeywordId from list_saved_keywords, or a plain keyword to look it up before saving: that saves and tracks nothing. A plain keyword uses the priority market unless you pass both locationCode and languageCode. Related: save_keywords, research_keywords.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "check_keyword_audience"
  }
}

Input Schema

Name	Required	Description
`keyword`	No	A keyword to look up without saving it.
`languageCode`	No	Language code, with keyword only. Defaults to the priority market.
`locationCode`	No	DataForSEO location, with keyword only. Defaults to the priority market.
`savedKeywordId`	No	Saved keyword id. Pass this or keyword, not both.

Output Schema

Name	Required	Description	Default
`summary`	Yes
`checkedAt`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 20, 2026

addedInput schema / properties / keyword

Added value: +{
+  "description": "A keyword to look up without saving it.",
+  "minLength": 1,
+  "type": "string"
+}

addedInput schema / properties / languageCode

Added value: +{
+  "description": "Language code, with keyword only. Defaults to the priority market.",
+  "minLength": 1,
+  "type": "string"
+}

addedInput schema / properties / locationCode

Added value: +{
+  "description": "DataForSEO location, with keyword only. Defaults to the priority market.",
+  "maximum": 9007199254740991,
+  "minimum": -9007199254740991,
+  "type": "integer"
+}

changedInput schema / properties / savedKeywordId / description

Previous value: -"Saved keyword id."New value: +"Saved keyword id. Pass this or keyword, not both."

removedInput schema / required

Removed value: -[
-  "savedKeywordId"
-]

First observedOct 1, 2026

TDQS

A4.3/5.0

Behavior4/5

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

The description adds important behavior beyond annotations: each call is one search, fetches live Google top 10 results, spends provider calls, and a plain keyword does not save or track anything. This is valuable cost and side-effect context, though auth and rate-limit details are not covered.

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?

The description is compact and front-loads purpose before cost and parameter guidance. It is slightly fragmented and repeats the cost idea, but every sentence provides useful operational context.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the output schema and annotations, the description covers what an agent needs before calling: purpose, cost, live search behavior, saved-vs-unsaved keyword modes, market defaults, and related tools. No major invocation detail is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although the schema already documents all four parameters, the description adds meaningful semantics: savedKeywordId should come from list_saved_keywords, keyword is for unsaved lookups, and locationCode/languageCode only override the priority market when both are passed. These interaction rules go beyond the raw schema.

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?

The description clearly states the specific action and resource: it fetches the current Google top 10 for a keyword to judge audience match. It is much clearer than the name alone, though sibling differentiation from tools like get_rankings or research_keywords is only implied through 'Related' rather than made explicit.

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?

It gives clear usage context: pass a savedKeywordId from list_saved_keywords or a plain keyword for a pre-save lookup, and notes that plain-keyword lookups save and track nothing. Related tools are named, but there is no explicit when-not or comparative guidance beyond those hints.

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

All Mark tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?