Skip to main content
Glama
Sign In

Fudge for Shopify

by ai.fudge
OverviewDiscussionsAdmin

Get keyword metrics

get_keyword_metrics
Read-onlyIdempotent

Get Google search volume, difficulty, intent, CPC and 12-month history for specific keywords in one country. Missing values are unknown, not zero. Changes nothing and uses no credits; each store has a daily limit.

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": {
      "location": "<location>",
      "keywords": "<keywords>"
    },
    "name": "get_keyword_metrics"
  }
}

Input Schema

NameRequiredDescriptionDefault
storeNoThe connected store to use. Omit when only one is connected.
keywordsYes
languageNoLanguage code, e.g. "en". Defaults to the store’s language.
locationYesTarget country, e.g. "United States". Ask the merchant which countries they sell to if unknown.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so 'changes nothing' is largely redundant. The description does add real behavior beyond the annotations: no credit consumption, a per-store daily limit (rate limiting), and the critical semantics that missing values mean 'unknown, not zero'.

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?

Three tight sentences, front-loaded with the returned metrics, then edge-case semantics, then cost/limits. Slightly wasteful in that 'Changes nothing' restates the readOnly annotation, but no sentence is genuinely dispensable.

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?

With no output schema, the description carries the return-value burden and does it well by enumerating the metric families and the 12-month history, plus null-vs-zero handling. The remaining gap is that it never says what a response looks like structurally (per-keyword object, ordering) or how it behaves when a keyword has no data at all.

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?

At 75% schema coverage the schema already documents store, language and location. The description contributes the useful constraint that location is a single country ('in one country'), reinforcing the one-country scoping, but adds nothing about the keywords array (up to 50, no empty strings) or about language defaulting.

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?

Names a specific verb ('Get') and a precise resource set (Google search volume, difficulty, intent, CPC, 12-month history) scoped to 'specific keywords in one country'. The phrase 'for specific keywords' implicitly separates it from idea-generation siblings like find_keyword_ideas or find_keyword_ideas-style tools, but no sibling is named explicitly, so it stops just short of a 5.

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

Usage Guidelines3/5

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

Usage is only implied: the agent can infer this is the lookup tool for keywords it already has, versus discovery tools. There is no explicit 'use this when… / use X instead when…' statement, and no mention of prerequisites such as needing a connected store first.

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

All Fudge for Shopify 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