Skip to main content
Glama
shopify-partners-mcp

shopify-partners-mcp

by amitray007

get_active_subscription

Read-only

Retrieves a shop's active subscription for a specified app using Shopify managed pricing, so you can verify current billing status.

Instructions

Get a shop's active subscription for an app that uses Shopify managed pricing.

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": {
      "appId": "<appId>",
      "shopId": "<shopId>"
    },
    "name": "get_active_subscription"
  }
}

Input Schema

NameRequiredDescriptionDefault
appIdYesApp ID: the number or a gid:// ID
shopIdYesShop ID: the number or a gid:// ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds a real behavioral constraint (only apps on Shopify managed pricing), but omits what is returned when no active subscription exists — a null result versus an error — which is the main behavioral unknown for a lookup tool with no output schema.

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?

A single sentence with no filler, and the scope-qualifying clause follows immediately after the core action. Nothing could be removed without losing 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 simple two-parameter read, the description covers purpose and the key applicability constraint, and the annotations cover safety. With no output schema, though, an agent still cannot tell what the response looks like or how an absence of an active subscription is signaled, which leaves a meaningful gap.

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 100%: appId and shopId are both described in the schema, including that they accept a number or a gid:// ID. The description adds no parameter meaning beyond that, so the baseline of 3 applies.

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?

States a specific verb and resource ("Get a shop's active subscription") plus the qualifying context of Shopify managed pricing apps, so the agent knows exactly what is retrieved. It does not distinguish itself from any sibling, but none of the listed siblings appear to overlap on subscription retrieval, so the gap is minor.

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?

The phrase "for an app that uses Shopify managed pricing" acts as an implicit precondition for use, which is genuine guidance. However, there is no statement of when not to use it, what to call instead for non-managed-pricing apps, or what happens when a shop has no active subscription.

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