Skip to main content
Glama

Mark

by com.use-mark.app
OverviewDiscussionsAdmin

Check Keyword Audience

check_keyword_audience
Read-onlyIdempotent

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. 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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keywordNoA keyword to look up without saving it.
languageCodeNoLanguage code, with keyword only. Defaults to the priority market.
locationCodeNoDataForSEO location, with keyword only. Defaults to the priority market.
savedKeywordIdNoSaved keyword id. Pass this or keyword, not both.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
summaryYes
checkedAtYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • 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"
-]
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, openWorld. The description adds value beyond them: 'Each call is 1 search' discloses a per-call cost, and 'that saves and tracks nothing' explicitly disambiguates the side-effect-free plain-keyword path.

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?

Two sentences with the core purpose front-loaded, followed by a compressed related-tools line. Efficient overall, though the bare 'Related:' prefix lists tool names without explaining the relationship, which slightly weakens the closing line.

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 need no explanation, and annotations carry the safety profile. The description covers both input paths, market defaults, and side effects, leaving only the explicit this-vs-siblings routing gap.

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 coverage is 100%, so baseline is 3. The description adds real meaning: savedKeywordId should come from list_saved_keywords, and a plain keyword uses the priority market unless both locationCode and languageCode are supplied. That interaction is not fully spelled out in the schema alone.

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?

States a specific verb and resource: it fetches who currently ranks for a keyword and judges whether those searchers match the audience. The scope ('current Google top 10') is concrete, and it names related tools (save_keywords, research_keywords) so the agent can place it among siblings.

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 explicit behavioral routing between the two input modes: pass a savedKeywordId from list_saved_keywords, or a plain keyword to look it up without saving/tracking. However, 'Related: save_keywords, research_keywords' does not state the condition under which the agent should prefer this tool over those alternatives.

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

All Mark toolsInspect
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