Skip to main content
Glama
shopify-partners-mcp

shopify-partners-mcp

by amitray007

run_query

Read-only

Execute read-only GraphQL queries against the Shopify Partner API to fetch data other tools miss. Mutations are rejected, so queries remain read-only.

Instructions

Run a read-only GraphQL query against the Partner API for anything the other tools miss. Mutations are rejected.

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": {
      "query": "<query>"
    },
    "name": "run_query"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesA GraphQL query document
variablesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint; the description adds genuine value by stating that mutations are rejected at the API level, which matters because a GraphQL endpoint would normally accept them. It omits other traits an arbitrary-query tool needs disclosed: authentication/permission scope of the partner token, query complexity or rate limits, and how errors surface.

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, zero filler, with the core capability and the fallback role front-loaded before the mutation caveat. Every clause carries information.

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 generic escape-hatch tool with no output schema and a nested `variables` object, the definition never indicates what is queryable on the Partner API, whether introspection is permitted, or how results and errors are returned. The agent is told when to use it but not enough to construct a valid query with confidence.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With only 50% schema description coverage, the description must compensate for the undocumented `variables` parameter, and it does not — there is no mention of how variables bind to the query or what types are accepted. The one sentence about queries adds nothing beyond the schema's own 'A GraphQL query document' for `query`.

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?

States a specific verb and resource ('Run a read-only GraphQL query against the Partner API') and explicitly positions itself as the catch-all fallback ('for anything the other tools miss'), which separates it from every named analytics sibling. An agent can tell instantly that this is the escape hatch, not a specialized report tool.

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 clear when-to-use rule (when the other tools don't cover the need) and a when-not rule (mutations are rejected), which is exactly the failure mode an agent would otherwise hit. It stops short of naming which specific gaps this is best for or warning about query cost/complexity limits, so it is strong but not exhaustive.

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