Skip to main content
Glama
storelift-mcp

storelift-mcp

Stored keyword metrics

hive_keyword_metrics
Read-onlyIdempotent

Reads stored popularity and difficulty scores for one exact keyword in a chosen storefront, with evidence, freshness and status per metric. Read-only; it never starts a measurement.

Instructions

Read the stored popularity (integer 1–100) and difficulty (0–100) of one exact keyword in one storefront. Each metric has its own evidence, source time, freshness and last-attempt status; a missing value stays null and is never zero. This read never starts a measurement — use hive_measure_keyword_metrics for that. iOS only.

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": {
      "term": "<term>"
    },
    "name": "hive_keyword_metrics"
  }
}

Input Schema

NameRequiredDescriptionDefault
termYesexact keyword, e.g. habit tracker
countryNostorefront code, e.g. us (defaults to us)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint/idempotentHint/non-destructive, but the description adds real behavioral detail beyond them: null-vs-zero semantics for missing values, per-metric evidence, source time, freshness and last-attempt status, and the guarantee that calling it triggers no measurement. That is the kind of context an agent needs to interpret results correctly.

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, front-loaded with the core action and value ranges, then the null semantics, then the alternative-tool routing and platform note. No redundant or filler phrasing.

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?

There is no output schema, yet the description still characterizes what comes back (two metrics with ranges, plus per-metric evidence, source time, freshness and status). Combined with the explicit non-mutating guarantee and platform constraint, an agent has everything needed to call it correctly.

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 coverage is 100%, so the baseline is 3. The description reinforces 'one exact keyword' and 'one storefront' but adds no new syntax, format, or default information beyond what the schema's 100%-covered parameter descriptions already say.

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?

The description opens with a specific verb and resource: 'Read the stored popularity (integer 1–100) and difficulty (0–100) of one exact keyword in one storefront.' It even specifies value ranges and the one-keyword/one-storefront scope, which lets an agent distinguish it from a measuring tool without opening the schema.

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?

It states an explicit boundary ('This read never starts a measurement') and names the alternative to use instead ('hive_measure_keyword_metrics'), plus a platform restriction ('iOS only'). Both when-to-use and when-not-to-use are covered with a named sibling.

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