Skip to main content
Glama
Sign In

Fudge for Shopify

by ai.fudge
OverviewDiscussionsAdmin

Find keyword ideas

find_keyword_ideas
Read-onlyIdempotent

Find longer search phrases containing a seed keyword, with volume, difficulty and intent. 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>",
      "seed": "<seed>"
    },
    "name": "find_keyword_ideas"
  }
}

Input Schema

NameRequiredDescriptionDefault
seedYes
limitNo
storeNoThe connected store to use. Omit when only one is connected.
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.
minVolumeNo
maxDifficultyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

The annotations already state that the tool is read-only, idempotent, non-destructive, and touches an open world, so the description is clear about safety. It still adds real value by naming a credit cost and a per-store daily limit, which annotations cannot express. It does not describe pagination or how many results come back beyond the limit parameter.

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 short sentences open with the core purpose and then state the cost constraint; nothing is wasted. Both the scope and the caveats are easy to scan.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 7-parameter tool with no output schema, the description covers purpose and cost and limit behavior well, but leaves the filtering parameters (limit, minVolume, maxDifficulty) unexplained even though they materially shape the results. It is adequate, not complete.

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 only 43%, so half the parameters (seed, limit, minVolume, maxDifficulty) have no schema-level documentation. The description hints at the seed and at volume and difficulty, but those are framed as output fields rather than as filters the caller can set. The description does not compensate for the coverage gap.

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?

The description gives a specific verb and resource: it finds 'longer search phrases containing a seed keyword' and previews the returned fields (volume, difficulty, intent). That is enough to separate it from generic metric or ranking tools, though no sibling is named, so the boundary with get_keyword_metrics or get_ranked_keywords has to be inferred.

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

Usage Guidelines2/5

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

The description says what the tool is, but not when to pick it over the keyword tools in the sibling list, and it names no exclusions or prerequisites. An agent can infer it is for discovery from a seed phrase, but must open the schemas to decide between the keyword-family tools.

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