Skip to main content
Glama
Sign In

AppmanAi

by com.appmanai
OverviewDiscussionsAdmin

Keyword popularity scores in bulk

keyword_metrics_sap_batch
Read-only

Get the search-ads popularity (SAP) of many keywords in one call. Use it to rank a whole keyword list by demand before profiling the promising ones. Costs 9 credits.

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": {
      "country": "<country>",
      "keywords": "<keywords>"
    },
    "name": "keyword_metrics_sap_batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryYesTwo-letter ISO country code, e.g. "US", "GB", "DE".
keywordsYesSearch terms, up to 50, e.g. ["habit tracker", "daily planner"].

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuinely new behavioral context by disclosing the 'Costs 9 credits' charge, which the annotations do not convey. It stops short of describing return format or ordering, so not 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences: purpose first, then workflow guidance, then cost. Each sentence carries distinct information with zero waste and the key purpose is front-loaded.

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?

For a two-parameter read-only batch tool with full schema coverage and safety annotations, the description covers purpose, usage and cost adequately. The only modest gap is that it doesn't clarify the shape of the returned SAP scores per keyword, though no output schema exists to carry that.

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% and both parameters (country, keywords with 50-item cap) are fully documented in the schema. The description adds no syntax or format meaning beyond what the schema already provides, so the baseline 3 applies.

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 ('Get the search-ads popularity') and resource ('many keywords in one call'), and the 'in one call' / 'many keywords' framing implicitly distinguishes it from the singular keyword_metrics_sap sibling. It never names that sibling explicitly, so differentiation is inferred rather than stated.

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?

'Use it to rank a whole keyword list by demand before profiling the promising ones' gives a clear workflow context: bulk ranking first, then detailed profiling (the single-tool step). It implies the alternative without naming it and offers no explicit exclusions, keeping it below a 5.

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

All AppmanAi 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