Skip to main content
Glama
Sign In

Fudge for Shopify

by ai.fudge
OverviewDiscussionsAdmin

Get ranked keywords

get_ranked_keywords
Read-onlyIdempotent

List the Google searches a domain ranks for in one country, with position, URL, volume, difficulty and estimated traffic. Defaults to this store; pass a competitor’s domain to compare. 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>"
    },
    "name": "get_ranked_keywords"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
storeNoThe connected store to use. Omit when only one is connected.
domainNoDefaults to this store’s domain.
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.
pathPrefixNoOnly URLs under this path, e.g. /blogs/.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false), so the description's real contribution is the cost and quota disclosure: "uses no credits; each store has a daily limit." That is behavior the agent cannot get from structured fields. It does not say what happens when the daily limit is hit, which keeps it from 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?

Two sentences with zero filler. The primary capability and its output fields come first, and the default/competitor routing plus the credit and quota note are packed into the second.

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 correctly compensates by naming what is returned (position, URL, volume, difficulty, estimated traffic). Combined with the disclosed rate limit and store/competitor framing, an agent has enough to invoke it correctly. Remaining gaps (limit behavior, what happens at the daily cap) are minor.

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 83%, so the schema baseline already carries most parameter meaning. The description still adds value by framing the domain parameter as the competitor-comparison lever and reinforcing the single-country constraint on location. The limit and pathPrefix parameters get no extra context, but the schema already documents them.

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?

Specific verb and resource ("List the Google searches a domain ranks for") plus an explicit scope constraint ("in one country") and an enumeration of returned fields. This is clearly distinct from sibling tools like get_keyword_metrics or find_keyword_ideas, though the description never names an alternative to sharpen the contrast.

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 a concrete usage pattern: default to this store versus "pass a competitor's domain to compare." That tells the agent both the default path and the comparison use case. It stops short of naming when to use a sibling tool instead, so no explicit exclusion is present.

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