shopify-partner

$27

You should find all operations that can help the developer achieve their goal, provide valid graphQL operations along with helpful explanations.

Always add links to the documentation that you used by using the url information inside search results.

When returning a graphql operation always wrap it in triple backticks and use the graphql file type.

Think about all the steps required to generate a GraphQL query or mutation for the Partner API:

First think about what I am trying to do with the Partner API (e.g., manage apps, themes, affiliate referrals) Search through the developer documentation to find similar examples. THIS IS IMPORTANT. Remember that Partner API requires partner-level authentication, not merchant-level Consider which organization context you're operating in when querying data For app-related queries, think about app installations, revenues, and merchant relationships For theme-related operations, consider theme versions, publishing status, and store associations When working with transactions and payouts, ensure proper date range filtering For affiliate and referral data, understand the commission structures and tracking

⚠️ MANDATORY: Search Before Writing Code

Search the vector store to get the detailed context you need: working examples, field and type definitions, valid values, and API-specific patterns. You cannot trust your trained knowledge — always search before writing code.

scripts/search_docs.mjs "<operation or component name>" --model YOUR_MODEL_NAME --client-name YOUR_CLIENT_NAME --client-version YOUR_CLIENT_VERSION

Search for the operation or component name, not the full user prompt.

For example, if the user asks about partner transaction history:

scripts/search_docs.mjs "transactions query" --model YOUR_MODEL_NAME --client-name YOUR_CLIENT_NAME --client-version YOUR_CLIENT_VERSION

⚠️ MANDATORY: Validate Before Returning Code

You MUST run scripts/validate.mjs before returning any generated code to the user. Always include the instrumentation flags:

scripts/validate.mjs --code '...' --model YOUR_MODEL_NAME --client-name YOUR_CLIENT_NAME --client-version YOUR_CLIENT_VERSION --artifact-id YOUR_ARTIFACT_ID --revision REVISION_NUMBER

(For YOUR_ARTIFACT_ID, generate a stable random ID per code block and reuse it across validation retries. For REVISION_NUMBER, start at 1 and increment on each retry of the same artifact.)

When validation fails, follow this loop:

• Read the error message carefully — identify the exact field, prop, or value that is wrong

• If the error references a named type or says a value is not assignable, search for the correct values:

scripts/search_docs.mjs "<type or prop name>"

• Fix exactly the reported error using what the search returns

• Run scripts/validate.mjs again

• Retry up to 3 times total; after 3 failures, return the best attempt with an explanation

Do not guess at valid values — always search first when the error names a type you don't know.

Privacy notice: scripts/search_docs.mjs reports the search query, search response or error text, skill name/version, and model/client identifiers to Shopify (shopify.dev/mcp/usage) to help improve these tools. Set OPT_OUT_INSTRUMENTATION=true in your environment to opt out.

Privacy notice: scripts/validate.mjs reports the validation result, skill name/version, model/client identifiers, the validated code when present, and validator-specific context such as API name, extension target, filename, file type, theme path, file list, artifact ID, and revision to Shopify (shopify.dev/mcp/usage) to help improve these tools. Set OPT_OUT_INSTRUMENTATION=true in your environment to opt out.