Skip to main content
Glama
shopify-partners-mcp

shopify-partners-mcp

by amitray007

list_transactions

Read-only

Lists earnings transactions—app, theme, service, referral, tax—newest first with pagination so you can review Shopify Partner financial activity. Requires View financials permission.

Instructions

List earnings transactions (app, theme, service, referral, tax), newest first, one page at a time. Needs the View financials permission.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_transactions"
  }
}

Input Schema

NameRequiredDescriptionDefault
afterNonextCursor from the previous page
appIdNoApp ID: the number or a gid:// ID
firstNoPage size, default 100
typesNoTransactionType values, e.g. APP_SUBSCRIPTION_SALE
shopIdNoShop ID: the number or a gid:// ID
createdAtMaxNoLatest creation time, ISO 8601
createdAtMinNoEarliest creation time, ISO 8601
myshopifyDomainNoFor example example.myshopify.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the description does not need to re-establish safety. It earns credit by adding what annotations cannot: the newest-first ordering, the fact that results come back one page at a time (relevant to the cursor/page-size params), and the required View financials permission.

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 with zero filler, front-loading what the tool returns and its ordering before the access requirement. Every clause carries information an agent needs.

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?

For an 8-parameter read-only listing with no output schema, the description covers data scope, ordering, pagination model, and permissions. The remaining gap is that it never mentions the appId/shopId/time-range filtering capability, which an agent would only discover from the schema.

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 description coverage is 100%, so parameters like after, first, appId, shopId, and the createdAt bounds are already documented. The description adds only marginal semantic value by listing the transaction categories that the `types` filter accepts; it says nothing about how to scope by app or shop or how to chain cursors.

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 ("List earnings transactions") and enumerates the transaction categories it covers, plus ordering and pagination shape. It is clearly distinguishable from aggregate siblings like earnings_by_month or revenue_summary, but it never names an alternative explicitly, so it stops 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 context is implied rather than stated: an agent can infer this is the raw transaction-level listing versus the summary/report siblings, and the "View financials permission" prerequisite is a useful gate. However, there is no explicit when-to-use/when-not guidance or named alternative.

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