Skip to main content
Glama
Sign In

Cite42: AI visibility and SEO data for AI agents

by dev.cite42
OverviewDiscussionsAdmin

cite42_keywords

Read-only

Classic keyword data for a seed term. Omit ideas (the default) when the user only needs that seed's volume, CPC, or competition. Set ideas:true only when the user asks for related, alternative, or long-tail suggestions from provider candidates. Billed in USD (result field cite42Billing) to the user's prepaid Cite42 balance, and failed calls are free; exact prices from cite42_pricing (free). For plans over 20 calls or $5, estimate the cost and confirm with the user first.

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": {
      "seed": "<seed>"
    },
    "name": "cite42_keywords"
  }
}

Input Schema

NameRequiredDescriptionDefault
seedYesSeed keyword to fetch search volume, CPC, and competition for.
ideasNoLeave false for volume, CPC, and competition on the seed only. Set true only when related, alternative, or long-tail keyword ideas are requested.
countryNoISO-2 country code for localized metrics. Defaults to "us".us
languageNoOptional ISO-2 language code. Defaults to the country's primary search language, so country "de" searches in German. Only multilingual markets accept an override: us (en, es), ca (en, fr), in (en, hi). Every other country has a single search language and rejects anything else.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld/non-destructive, but the description adds what the schema cannot: billing in USD to a prepaid balance, that failed calls are free, the name of the billing result field (cite42Billing), and a cost-confirmation threshold. The only real gap is that it does not describe the shape of the returned keyword metrics beyond the billing field.

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, then usage of the `ideas` flag, then cost behavior — a sensible priority order with no filler. Slightly dense across four sentences ('Classic' is doing vague work in the opener), but every sentence carries actionable information.

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?

For a 4-parameter read-only lookup with no output schema and full schema coverage, the description covers purpose, mode selection, localization defaults (via schema), and the cost/confirmation model. Nothing an agent needs in order to call it correctly or warn the user about spend is missing.

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%, so `seed`, `ideas`, `country`, and `language` are already well documented in the schema itself. The description reinforces the intent of the `ideas` flag and mentions the billing result field, but adds no format or constraint detail beyond structured fields — 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 resource and operation: 'Classic keyword data for a seed term', with the default mode (volume, CPC, competition) spelled out. It cleanly separates the seed-metrics mode from the ideas mode, though it never names the obvious sibling cite42_keywords_batch, so an agent must infer which tool to use for multi-seed work.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit when/when-not guidance for the central `ideas` flag: omit when the user only needs the seed's metrics, set true only when related/alternative/long-tail suggestions are requested. It also routes the agent to cite42_pricing for exact prices and adds a pre-call confirmation rule for plans over 20 calls or $5.

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

All Cite42: AI visibility and SEO data for AI agents 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